手机官网               官方微信

搜索
   

OA联通入口      OA电信入口      

include error,path:/comp/nav/main?compId=nav_main-15108275524786096 cause:org.springframework.web.util.NestedServletException: Request processing failed; nested exception is com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method findFrontSubNode in the service cn.ce.ebiz.column.service.ColumnContentService. Tried 2 times of the providers [192.168.15.213:20881, 192.168.215.155:20881] (2/16) from the registry BJ-ZW-PAAS-MIDD-ZK-NODE4.online.local:2181 on the consumer 172.20.1.31 using the dubbo version 2.6.0. Last error is: Failed to invoke remote method: findFrontSubNode, provider: dubbo://192.168.215.155:20881/cn.ce.ebiz.column.service.ColumnContentService?anyhost=true&application=front&check=false&default.check=false&default.reference.filter=cecontext&default.retries=1&default.service.filter=cecontext&default.timeout=1000&dispatcher=message&dubbo=2.6.0&generic=false&interface=cn.ce.ebiz.column.service.ColumnContentService&loadbalance=roundrobin&methods=update,updatePostion,findByNav,deletebyNavId,get,deleteSingleColumn,findAll,getBreadcrumbColumnData,getCategoryTree,add,updateMove,findAsyncColumnTree,findByPagination,getMainNavColunmn,delete,findFrontSubNode,updateShowState,updateBefore,findChindren&owner=ebiz&pid=24954®ister.ip=172.20.1.31&remote.timestamp=1527586365816&revision=1.0.0-SNAPSHOT&side=consumer&timeout=1000×tamp=1527622777710, 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

地址:河南省洛阳市王城大道48号
电话:0379-63346998
传真:0379-63346969
网址:www.nwcorazon.com
邮箱:hnljly@vip.sina.com

 

Copyright © dafabet888手机官网    豫ICP备17047411号    网站建设:中企动力 洛阳     后台管理

新闻动态

News Center

include error,path:/comp/breadcrumb/nav?compId=breadcrumb_nav-1526035540663 cause:org.springframework.web.util.NestedServletException: Request processing failed; nested exception is com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method findPageNameById in the service cn.ce.ebiz.config.service.SiteConfigService. Tried 2 times of the providers [192.168.79.63:20881, 192.168.69.145:20881] (2/16) from the registry BJ-ZW-PAAS-MIDD-ZK-NODE4.online.local:2181 on the consumer 172.20.1.31 using the dubbo version 2.6.0. Last error is: Invoke remote method timeout. method: findPageNameById, provider: dubbo://192.168.79.63: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=1000&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=24954®ister.ip=172.20.1.31&remote.timestamp=1527586279294&revision=1.0.0-SNAPSHOT&side=consumer&timeout=1000×tamp=1527622778015, cause: Waiting server-side response timeout by scan timer. start time: 2018-05-30 04:14:40.772, end time: 2018-05-30 04:14:41.801, client elapsed: 0 ms, server elapsed: 1029 ms, timeout: 1000 ms, request: Request [id=138548, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=findPageNameById, parameterTypes=[class java.lang.String], arguments=[af96174b-39ab-430a-a049-013fbaedc3e4], attachments={consumerApplicationName=front, tenantId=22060, mobileRunning=true, pcRunning=true, appId=0, currentDomain=http://www.nwcorazon.com, productMode=true, sourceApp=1, consumerHostIp=192.168.69.145, interface=cn.ce.ebiz.config.service.SiteConfigService, consumerOsName=Linux, viewType=1, sw3=, version=0.0.0, formal=true, useViewType=true, path=cn.ce.ebiz.config.service.SiteConfigService, timeout=1000, consumerJavaRuntimeVersion=1.7.0_79-b15, consumerOsVersion=3.10.0-327.el7.x86_64}]], channel: /172.20.1.31:45015 -> /192.168.79.63:20881

集团公司举办混凝土耐久性与裂缝控制技术交流会

  集团公司举办混凝土耐久性与裂缝控制技术交流会

  2018年1月29日,混凝土耐久性与裂缝控制技术交流会在集团公司六楼会议室举行。中国土木工程学会混凝土质量专业委员会专家委员,中国建研建材源锦技术中心副主任纪宪坤博士主讲,各分公司主任工程师、项目技术负责人、施工员、质检员以及实验室、混凝土搅拌站技术人员近140余人次参加交流会。

  混凝土耐久性及裂缝控制问题是工程建设中的重难点问题,而混凝土裂缝是影响混凝土耐久性的重要因素。纪博士从混凝土开裂的原因、施工控制措施、裂缝控制技术三个方面进行了讲解。混凝土开裂的原因可分为塑性收缩、化学收缩、干燥收缩、温度收缩、材料的特质五类。根据裂缝成因,在施工中可以从合理使用粉煤灰矿粉、控制水灰比、加强养护等方面控制混凝土开裂。纪博士还介绍了补偿收缩混凝土技术、水化热调控技术在混凝土裂缝控制中的应用,并结合青岛万达影视摄影棚工程、北京新机场航站楼工程说明新技术的应用效果。最后纪博士回答了现场参会人员关于施工过程中遇到的相关问题。

  这次交流会使集团公司工程技术人员进一步明晰了混凝土裂缝的成因,了解混凝土裂缝控制的新技术、新措施,为今后施工过程中混凝土裂缝控制提供了经验和思路。 (技术部)