[
https://issues.apache.org/jira/browse/DIRMINA-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRMINA-760.
---------------------------------------
Resolution: Invalid
When a peer brutally close its side of the connection, there is no way for the
other peer to know about it. This is teh way TCP qworks. The only solution is
to periodically 'test' the connection : if it has been closed by the other
peer, you'll get an error. This is why we do have a {{KeepAlive}} filter, or a
{{sessionIdle()}} event : to be able to detect this use case.
> Client fails to detect disconnection
> ------------------------------------
>
> Key: DIRMINA-760
> URL: https://issues.apache.org/jira/browse/DIRMINA-760
> Project: MINA
> Issue Type: Bug
> Components: Core
> Reporter: Omry Yadan
> Fix For: 2.0.8
>
>
> Tested against revision 901694 (which is a bit after 2.0.0-RC1)
> My client need to maintain an open connection to the server.
> If I kill the server right before calling session.write(), the client does
> not detect that the server is gone.
> there is no exceptionCaught event, and messageSent is actually called (which
> suggests successful delivery).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
