Bisocket client cannot detect connection failure
------------------------------------------------
Key: JBREM-1140
URL:
https://jira.jboss.org/jira/browse/JBREM-1140
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: transport
Reporter: David Lloyd
Assignee: David Lloyd
Fix For: 2.2.3.SP1
The BisocketClientInvoker never reads from the control socket. Therefore, it might take a
long time for it to notice that the control connection dies, causing confusion between the
client and server (for example, the client may reuse a listener ID that the server
considers extinct). By adding a ping reply mechanism, the client must both send and
receive a ping for the connection to be known "good", which should help speed up
the dead connection detection process.
Since this change is protocol-incompatible, it should be enabled by a configuration
option. I'm using Bisocket.ENABLE_PING_REPLY = "enablePingReply" for this
purpose.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira