[
https://issues.apache.org/jira/browse/DIRMINA-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15422884#comment-15422884
]
Omry Yadan edited comment on DIRMINA-760 at 8/16/16 3:30 PM:
-------------------------------------------------------------
Emmanuel,
Quoting the task:
"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)."
TCP does support detection of this scenario pretty reliably because the
session.write() is equivalent to a connection test.
I don't really care at this point other way, but it feels like a wrong
resolution.
was (Author: omry):
Emanuel,
Quoting the task:
"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)."
TCP does support detection of this scenario pretty reliably because the
session.write() is equivalent to a connection test.
I don't really care at this point other way, but it feels like a wrong
resolution.
> 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)
