[
https://issues.apache.org/jira/browse/DIRMINA-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14386952#comment-14386952
]
Antoine Tran edited comment on DIRMINA-760 at 3/30/15 4:40 PM:
---------------------------------------------------------------
I confirm this issue with the latest version 2.0.9. I did what the author did.
The exceptionCaught is not called, but I have not tested if messageSent was
called.
Moreover, I can add that at the socket level, when I killed the server process,
the client socket status was ESTABLISHED, then disappeared from netstat. So
Mina should be able to detect disconnection, at least in this scenario.
My test environment is Linux Red Hat 6.5.
Any info of when or what we can do as a workaround ? This issue is very
important for us. Thank you.
was (Author: antoine.tran):
I confirm this issue with the latest version 2.0.9. I did what the author did.
The exceptionCaught is not called, but I have not tested if messageSent was
called.
Moreover, I can add that at the socket level, when I killed the server process,
the client socket status was ESTABLISHED, then disappeared from netstat.
My test environment is Linux Red Hat 6.5.
Any info of when or what we can do as a workaround ? This issue is very
important for us. Thank you.
> 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)
