include error,path:/comp/nav/main?compId=nav_main-14967124189514345 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.79.52:20881, 192.168.4.1:20881] (2/18) from the registry BJ-ZW-PAAS-MIDD-ZK-NODE4.online.local:2181 on the consumer 172.20.1.86 using the dubbo version 2.6.0. Last error is: Failed to invoke remote method: findFrontSubNode, provider: dubbo://192.168.4.1: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=18341®ister.ip=172.20.1.86&remote.timestamp=1527214165720&revision=1.0.0-SNAPSHOT&side=consumer&timeout=1000×tamp=1527276732612, 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
地址:广东省广州市天河区天河路228号
广晟大厦901
COPYRIGHT 2017-2021 广东瑞普科技股份有限公司 | 粤ICP备16104266号-1
关注瑞普手机官网
关注瑞普官方微信
电话:020-38330668
技术支持邮箱:services@gdreap.com

关于瑞普

产品中心

新闻资讯

服务热线:400-880-7200
  • 新闻资讯

资讯详情

瑞普科技:突破传统 追求最大效率云管理

分类:
行业新闻
作者:
来源:
2017-09-07
瑞普科技:突破传统 追求最大效率云管理
近日,专注于行业信息化以及系统集成服务供应商广东瑞普科技股份有限公司举办了“先进云管理的探索与创新”——产品发布探讨会。本次会议邀请到各大云管理开发研究团队,就此次产品发布提出各大家的综合意见以及产品感受,各大精英团队齐聚一堂,各抒己见,共同为云管理领域的创新进行了深度交流,一切都是为了更好的研发出适用于各大领域的云管理平台,加速建设国家信息化智能管理。
  瑞普科技通过此次会议展示了瑞普科技的最新研发成果:瑞普科技云管理平台。演示产品应用场景和解决方案。瑞普科技相关负责人表示:瑞普科技会不断改革创新,为客户提供一个多元化整体的管理系统和服务。并宣称瑞普科技云管理平台会突破以往的传统云管理,追求最大效率的云管理。
  目前大多数客户在传统的IT资源云管理化中共同面临着几大挑战,瑞普科技始终秉承着创新与突破的研发概念,突破了传统IT云管理中的几大挑战,让客户刨除了传统私有云以往资源利用率低、成本过高、环境部署困难、资源业务管理复杂以及落地实施困难等弊端,增强了兼容性、开放性、灵活性和扩展性,大大提升了客户在IT资源云管理化中的效率。主要功能有:角色与授权管理、云资源管理、虚拟机自动安装与部署、虚拟机镜像构造与管理、使用量计量与计费、部署与自动化服务、中间件模板部署、应用计量、Restful API、Power VC、灵活的开源业务流程引擎、IT运维与监控、服务目录管理以及动态资源池管理。
 

新闻中心

免责声明: 本站资料及图片来源互联网文章,本网不承担任何由内容信息所引起的争议和法律责任。所有作品版权归原创作者所有,与本站立场无关,如用户分享不慎侵犯了您的权益,请联系我们告知,我们将做删除处理!