欢迎进入福建省闽清新东方陶瓷有限公司官网!

推荐我们

关于我们  |  产品中心  |  新闻资讯  |  应用案例  |  招商加盟  |  联系我们     电话:13489999903  
版权所有 (c) 2017 福建省闽清新东方陶瓷有限公司       

include error,path:/comp/breadcrumb/nav?compId=breadcrumb_nav-1507644652355 cause:org.springframework.web.util.NestedServletException: Request processing failed; nested exception is com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method findPages in the service cn.ce.ebiz.config.service.SiteConfigService. Tried 2 times of the providers [192.168.12.87:20881, 192.168.12.118:20881] (2/19) from the registry 172.20.1.18:2181 on the consumer 172.20.4.67 using the dubbo version 2.6.0. Last error is: Failed to invoke remote method: findPages, provider: dubbo://192.168.12.87:20881/cn.ce.ebiz.config.service.SiteConfigService?anyhost=true&application=front&check=false&default.check=false&default.reference.filter=cecontext&default.retries=1&default.service.filter=cecontext&default.timeout=1500&dispatcher=message&dubbo=2.6.0&generic=false&interface=cn.ce.ebiz.config.service.SiteConfigService&loadbalance=roundrobin&methods=purgeCache,getLoginPage,getPagesWithCate,getCompListAll,getDetailPageByAppIdAndCateId,updatePageContent,getMOIndexPage,getDefaultFirstPageFileNameByAppIdAndCateId,deleteAllPage,getPageFileName,delbackUpTenant,getIntegratePage,findPagesByAppAndType,findPages,transJsonToDb,getPageCates,updatePagePerperty,addPageList,getPageByAppIdAndCateId,deletePage,updateElement,findPagesByTenantId,getPCIndexPage,updatePageList,findPageNameById,getPageInfoByPageId,getPageInfoByPhysicalName,getNoParameterPage,getbackUpTenant,getPagesWithExt,createPageTable,getAppIndexPage,addPage,publishPageList&owner=ebiz&pid=9878®ister.ip=172.20.4.67&remote.timestamp=1535709507254&revision=1.0.0-SNAPSHOT&side=consumer&timeout=1500×tamp=1535742221512, cause: com.alibaba.dubbo.remoting.ExecutionException: class com.alibaba.dubbo.remoting.transport.dispatcher.message.MessageOnlyChannelHandler error when process received event . com.alibaba.dubbo.remoting.ExecutionException: class com.alibaba.dubbo.remoting.transport.dispatcher.message.MessageOnlyChannelHandler error when process received event . at com.alibaba.dubbo.remoting.transport.dispatcher.message.MessageOnlyChannelHandler.received(MessageOnlyChannelHandler.java:44) at com.alibaba.dubbo.remoting.exchange.support.header.HeartbeatHandler.received(HeartbeatHandler.java:88) at com.alibaba.dubbo.remoting.transport.MultiMessageHandler.received(MultiMessageHandler.java:43) at com.alibaba.dubbo.remoting.transport.AbstractPeer.received(AbstractPeer.java:136) at com.alibaba.dubbo.remoting.transport.netty.NettyHandler.messageReceived(NettyHandler.java:90) at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:88) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296) at com.alibaba.dubbo.remoting.transport.netty.NettyCodecAdapter$InternalDecoder.messageReceived(NettyCodecAdapter.java:147) at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108) at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337) at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89) at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:714) at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:949) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1371) at com.alibaba.dubbo.remoting.transport.dispatcher.message.MessageOnlyChannelHandler.received(MessageOnlyChannelHandler.java:42) ... 24 more

新闻资讯

/ NEWS

浅谈全抛釉的特点与发展前景

据了解,全抛釉产品在行业的推动下,全抛釉已经进入了普及的阶段了。

现在谈论的已经不是全抛釉产品在瓷砖市场上是否流行方面了,而是全抛釉在未来市场上的发展前景方面。那么全抛釉为什么在市场上发展得那么快呢?

有关专业人士介绍,全抛釉很好地实现了不同类型瓷砖产品的特点相结合,完美实现了瓷砖的装饰性能及实用性能。

全抛釉拥有抛光砖与仿古砖的共同的特点,釉面上有着仿古砖复杂错综的图案,同时还拥有抛光砖光洁亮丽的表面。所以全抛釉不但很受欢迎,而且还会在以后瓷砖市场上占主导地位。

全抛釉符合人们的消费习惯 从国内环境来看,全抛釉的优点很符合人们现在快节奏的生活。随着经济的快速发展,人们的生活水平不断提高,生活节奏不断加快,很多人没有太多的时间享受愉悦、休闲的生活。这时,人们对瓷砖的选择更多会选具有仿古砖和抛光砖共同特点的全抛釉,而不是抛光砖或仿古砖。

全抛釉把装饰性能提升到了一个新的高度 在瓷砖的装饰方面,全抛釉的表现突出。在全抛釉工艺还没出现的时候,瓷砖的装饰整体上显得较为单调。但由于全抛釉在色泽和纹理方面实现了无可比拟的装饰性能,所以说,全抛釉的出现把装饰性能提升到了一个新的高度。