`
wb284551926
  • 浏览: 539108 次
文章分类
社区版块
存档分类
最新评论

[DUBBO] ChannelEventRunnable handle RECEIVED operation error, channel is NettyCh

阅读更多

某日在启动dubbo工程时,出现了下面的错误:

- | 2017-10-31 14:01:45.859 | WARN | IBP_DB_01 | DubboServerHandler-172.22.67.231:21881-thread-1 | c.a.d.r.t.d.ChannelEventRunnable > 62 |  |  |  [DUBBO] ChannelEventRunnable handle RECEIVED operation error, channel is NettyChannel [channel=[id: 0xf9182606, /127.0.0.1:56058 :> /127.0.0.1:21881]], message is status, dubbo version: dap-1.0, current host: 127.0.0.1 |

com.alibaba.dubbo.remoting.RemotingException: Failed to send message OK^M
dubbo> to /127.0.0.1:56058, cause: null
        at com.alibaba.dubbo.remoting.transport.netty.NettyChannel.send(NettyChannel.java:108)
        at com.alibaba.dubbo.remoting.transport.AbstractPeer.send(AbstractPeer.java:51)
        at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchangeHandler.received(HeaderExchangeHandler.java:185)
        at com.alibaba.dubbo.remoting.transport.DecodeHandler.received(DecodeHandler.java:52)
        at com.alibaba.dubbo.remoting.transport.dispatcher.ChannelEventRunnable.run(ChannelEventRunnable.java:82)
        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.nio.channels.ClosedChannelException: null
        at org.jboss.netty.channel.socket.nio.AbstractNioWorker.cleanUpWriteBuffer(AbstractNioWorker.java:433)
        at org.jboss.netty.channel.socket.nio.AbstractNioWorker.writeFromUserCode(AbstractNioWorker.java:128)
        at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleAcceptedSocket(NioServerSocketPipelineSink.java:99)
        at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:36)
        at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:779)
        at org.jboss.netty.channel.Channels.write(Channels.java:725)
        at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.doEncode(OneToOneEncoder.java:71)
        at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:59)
        at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
        at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:784)
        at org.jboss.netty.channel.SimpleChannelHandler.writeRequested(SimpleChannelHandler.java:292)
        at com.alibaba.dubbo.remoting.transport.netty.NettyHandler.writeRequested(NettyHandler.java:99)
        at org.jboss.netty.channel.SimpleChannelHandler.handleDownstream(SimpleChannelHandler.java:254)
        at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
        at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:582)
        at org.jboss.netty.channel.Channels.write(Channels.java:704)
        at org.jboss.netty.channel.Channels.write(Channels.java:671)
        at org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:348)
        at com.alibaba.dubbo.remoting.transport.netty.NettyChannel.send(NettyChannel.java:98)
        ... 7 common frames omitted
- | 2017-10-31 14:01:45.859 | INFO | IBP_DB_01 | DubboServerHandler-172.22.67.231:21881-thread-1 | c.a.d.r.protocol.dubbo.DubboProtocol > 42 |  |  |  [DUBBO] disconected from /127.0.0.1:56058,url:dubbo://172.22.67.231:21881/com.dap.sequence.SequenceGenerator?anyhost=true&application=sequence&channel.readonly.sent=true&codec=dubbo&default=true&default.queues=5000&default.retries=0&default.threadpool=cached&default.threads=200&default.timeout=10000&dubbo=dap-1.0&generic=false&heartbeat=60000&interface=com.dap.sequence.SequenceGenerator&logger=slf4j&methods=dropSequence,query,getSequence,queryDetail,createSequence,updateIncreasement,getBigIntSequence&pid=11388&revision=1.0.0-SNAPSHOT&side=provider&timestamp=1509429704834, dubbo version: dap-1.0, current host: 127.0.0.1 |

- | 2017-10-31 14:01:47.840 | WARN | IBP_DB_01 | New I/O worker #2 | c.a.d.r.transport.AbstractServer > 54 |  |  |  [DUBBO] All clients has discontected from /127.0.0.1:21881. You can graceful shutdown now., dubbo version: dap-1.0, current host: 127.0.0.1 |

而且,启动脚本方面还出现了下面的错误:

 

以上错误原因:根据排查,出现这种问题的机器的操作系统是redhat7,在redhat6上面没有发现此类问题。考虑到可能是nc的不同版本造成的。故试着把redhat6的nc安装到redhat7上面

处理办法:

1、卸载redhat7 上面的你nc包:rpm -e nmap-ncat-6.40-4.el7.x86_64 --nodeps

2、安装nc-1.84-24.el6.x86_64.rpm包:rpm -ivh nc-1.84-24.el6.x86_64.rpm

重新启动,不在出现上面的问题。

nc-1.84-24.el6.x86_64.rpm下载地址
http://mirror.centos.org/centos/6/os/x86_64/Packages/nc-1.84-24.el6.x86_64.rpm
原文地址:https://blog.csdn.net/gino725/article/details/78415693
分享到:
评论

相关推荐

    解决dubbo标签报错,原因是:缺少dubbo.xsd

    下载一个dubbo.xsd文件windows->preferrence->xml->xmlcatalog add->catalog entry ->file system 选择刚刚下载的文件路径 修改key值和配置文件的http://code.alibabatech.com/schema/dubbo/dubbo.xsd 相同 保存即可...

    系统稳定性——Dubbo 常见错误及解决方法1

    1. 访问注册中心的 Ops 系统,查询对应的服务是否有提供者列表 2. 如无,则表明发布者发布服务失败,检查发布者的应用启动是否成功 3. 如有服务,则检查调

    dubbo资源 dubbo-admin dubbo demo

    dubbo资源 dubbo-admin dubbo demo

    dubbo找不到dubbo.xsd报错

    - cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'dubbo:application'. - schema_reference.4: Failed to read schema document '...

    dubbo示例代码dubbo-sample

    dubbo示例代码dubbo-sample

    incubator-dubbo-dubbo-2.6.1

    incubator-dubbo-dubbo-2.6.1

    尚硅谷最新dubbo视频

    本套视频从分布式系统的基本概念出发,由浅入深,讲解了RPC原理,Dubbo基本使用,Dubbo高可用场景以及Dubbo原理,涉及了分布式系统中服务注册、服务发现、负载均衡、灰度发布、集群容错、服务降级等核心概念的讲解及...

    dubbodubbo.zip

    dubbo资源包

    dubbo视频教程|基于Dubbo的分布式系统架构实战

    Dubbo是阿里巴巴开源的分布式服务化治理框架(微服务框架),久经阿里巴巴电商平台的大规模复杂业务的高并发考验,到目前为止Dubbo仍然是开源界中体系最完善的服务化治理框架,因此Dubbo被国内大量的的互联网公司和...

    dubbo接口测试调试工具

    前段时间排查某问题的时候,想要快速知道某些dubbo接口(三无)的响应结果,但不想启动项目(因为这些项目不是你负责的,不会部署而且超级笨重),也不想新建一个dubbo客户端项目(占地方),也不想开telnet客户端...

    使用dubbo时需要的dubbo.xsd

    使用 dubbo 时需要添加 dubbo 支持,否则会报错 。cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'dubbo:application'.

    dubbo-master

    On the server side, the server implements this interface and runs a dubbo server to handle client calls. On the client side, the client has a stub that provides the same methods as the server.

    解决dubbo找不到dubbo.xsd报错

    - cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'dubbo:application'. - schema_reference.4: Failed to read schema document '...

    dubbo源码解析2

    dubbo源码解析2.dubbo源码解析2.dubbo源码解析2.dubbo源码解析2.dubbo源码解析2.dubbo源码解析2.dubbo源码解析2.dubbo源码解析2.dubbo源码解析2.dubbo源码解析2.dubbo源码解析2.dubbo源码解析2.

    Dubbo培训与实战

    首先,从知识层面对Dubbo有一个了解和认识,请看《Dubbo培训与实战.pptx》,然后把Dubbo用到实际项目中来,请看实例代码《Dubbo实例代码(Sping+Dubbo+Maven).zip》,里面包括dubboDemoProvide和dubboDemoConsumer...

    dubbo捕获自定义异常_dubbo异常捕获_dubbo异常_自定义异常_捕捉异常_

    解决dubbo接口自定义异常的捕捉问题,dubbo消费者可以捕捉到提供者所抛出的自定义异常。

    【BAT必备】dubbo面试题

    【BAT必备】dubbo面试题【BAT必备】dubbo面试题【BAT必备】dubbo面试题【BAT必备】dubbo面试题【BAT必备】dubbo面试题【BAT必备】dubbo面试题【BAT必备】dubbo面试题【BAT必备】dubbo面试题【BAT必备】dubbo面试题...

    dubbo+zookeeper缓存方案

    dubbo+zookeeper缓存方案 dubbo+zookeeper缓存方案dubbo+zookeeper缓存方案dubbo+zookeeper缓存方案

    dubbo.xsd文件下载

    dubbo配置xml文件报错“Multiple annotations found at this line: - cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'dubbo:application'. - ...

Global site tag (gtag.js) - Google Analytics