Netty:关闭通道时出现ClosedChannelException
为什么当我尝试关闭通道时,会抛出 ChannelClosedException? 使用 Channel.close() 关闭,异常的堆栈跟踪:
java.nio.channels.ClosedChannelException
at org.jboss.netty.channel.socket.nio.NioWorker.cleanUpWriteBuffer(NioWorker.java:645)
at org.jboss.netty.channel.socket.nio.NioWorker.close(NioWorker.java:601)
at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleAcceptedSocket(NioServerSocketPipelineSink.java:119)
at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:76)
at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:60)
at org.jboss.netty.channel.Channels.close(Channels.java:720)
at org.jboss.netty.channel.AbstractChannel.close(AbstractChannel.java:200)
at ru.greencubes.player.PlayerWorkerThread.closeConnection(PlayerWorkerThread.java:107)
at ru.greencubes.player.PlayerWorkerThread.shutDown(PlayerWorkerThread.java:282)
at ru.greencubes.player.NetworkPlayerThread.disconnect(NetworkPlayerThread.java:1289)
at ru.greencubes.player.NetworkPlayerThread.disconnect(NetworkPlayerThread.java:1272)
at ru.greencubes.server.Server.run(Server.java:1590)
at ru.greencubes.server.ServerThread.run(ServerThread.java:12)
Why when i'm trying to close channel, I got ChannelClosedException thrown?
Closing with Channel.close(), exception's stacktrace:
java.nio.channels.ClosedChannelException
at org.jboss.netty.channel.socket.nio.NioWorker.cleanUpWriteBuffer(NioWorker.java:645)
at org.jboss.netty.channel.socket.nio.NioWorker.close(NioWorker.java:601)
at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleAcceptedSocket(NioServerSocketPipelineSink.java:119)
at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:76)
at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:60)
at org.jboss.netty.channel.Channels.close(Channels.java:720)
at org.jboss.netty.channel.AbstractChannel.close(AbstractChannel.java:200)
at ru.greencubes.player.PlayerWorkerThread.closeConnection(PlayerWorkerThread.java:107)
at ru.greencubes.player.PlayerWorkerThread.shutDown(PlayerWorkerThread.java:282)
at ru.greencubes.player.NetworkPlayerThread.disconnect(NetworkPlayerThread.java:1289)
at ru.greencubes.player.NetworkPlayerThread.disconnect(NetworkPlayerThread.java:1272)
at ru.greencubes.server.Server.run(Server.java:1590)
at ru.greencubes.server.ServerThread.run(ServerThread.java:12)
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
我认为你应该忽略这一点。它只是告诉您,当它尝试将剩余字节写入通道时,通道已经关闭。所以没什么好担心的。
I think you should just ignore this. It just told you that the channel was already closed when it tried to write the remaining bytes to the channel. So nothing to worry about.