Dubbo错误排查

最新推荐文章于 2024-01-18 05:00:00 发布

Ajekseg

最新推荐文章于 2024-01-18 05:00:00 发布

阅读量533

点赞数 1

分类专栏： java 文章标签： dubbo java 分布式大数据 intellij-idea

本文链接：https://blog.csdn.net/Ajekseg/article/details/126657939

版权

java 专栏收录该内容

306 篇文章 12 订阅

订阅专栏

这篇博客分析了一次Dubbo服务调用中出现的客户端超时和服务器端通道关闭的问题。客户端报错显示请求方法超时，而服务端警告显示无法向客户端发送响应，原因是通道被关闭。解决办法是检查并配置客户端超时时间，确保其设置合理。

摘要由CSDN通过智能技术生成

客户端错误：

com.alibaba.dubbo.rpc.RpcException: Invoke remote method timeout. method: searchUser, provider:
…

cause: Waiting server-side response timeout by scan timer. start time: 2015-06-17 14:46:49.979, end time: 2015-06-17 14:46:51.002, client elapsed: 44 ms, server elapsed: 959 ms, timeout: 1000 ms, request: Request

…

服务端警告：

2015-06-17 14:46:52,454 WARN [DubboServerHandler-172.25.6.248:20882-thread-2] (ChannelEventRunnable.java:84) - [DUBBO] ChannelEventRunnable handle RECEIVED operation error

com.alibaba.dubbo.remoting.RemotingException: Failed to send message Response [id=0, version=2.0.0, status=20, event=false, error=null, result=RpcResult [result=com.ceair.cesso.dto.SearchUserResult@7ba2a1d2, exception=null]] to /172.25.3.91:50849, 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:171)
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 $W or k er . r u n T a s k (T h re a d P oo lE x ec u t or . ja v a : 886) a t ja v a . u t i l . co n c u rre n t . T h re a d P oo lE x ec u t or$ Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.nio.channels.ClosedChannelException
at org.jboss.netty.channel.socket.nio.NioWorker.cleanUpWriteBuffer(NioWorker.java:643)
at org.jboss.netty.channel.socket.nio.NioWorker.writeFromUserCode(NioWorker.java:370)
at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleAcceptedSocket(NioServerSocketPipelineSink.java:137)
at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:76)
at org.jboss.netty.channel.Channels.write(Channels.java:632)
at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:70)
at com.alibaba.dubbo.remoting.transport.netty.NettyHandler.writeRequested(NettyHandler.java:99)
at org.jboss.netty.channel.Channels.write(Channels.java:611)
at org.jboss.netty.channel.Channels.write(Channels.java:578)
at org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:251)
at com.alibaba.dubbo.remoting.transport.netty.NettyChannel.send(NettyChannel.java:98)
… 7 more
原因分析