You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Rob Eden (JIRA)" <ji...@apache.org> on 2014/12/11 21:59:13 UTC
[jira] [Commented] (DIRMINA-785) Half-duplex close of TCP channel
[ https://issues.apache.org/jira/browse/DIRMINA-785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243128#comment-14243128 ]
Rob Eden commented on DIRMINA-785:
----------------------------------
Cool, but annoying that this change happened in a maintenance release as it broke all my IoHandlers. Changing the version to 2.1 would have been nice.
> Half-duplex close of TCP channel
> --------------------------------
>
> Key: DIRMINA-785
> URL: https://issues.apache.org/jira/browse/DIRMINA-785
> Project: MINA
> Issue Type: Bug
> Components: Transport
> Affects Versions: 2.0.0-M6
> Reporter: Jan Tauš
> Fix For: 2.0.8
>
> Attachments: patch-asyncweb-2.0.0-r942061.diff, patch-mina-2.0.0-RC1.diff
>
>
> Current MINA implementation doesn't support half-duplex close as described in RFC-793 section 3.5. "Closing a Connection".
> After the read in AbstractPollingIoProcessor#read() fails due to closed of the input stream whole NioSocketSession#channel is scheduled to close. In such situation only the input part should be closed with call to SocketChannel#socket().shutdownInput(). The whole channel should be closed only after the IoSession#close() call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)