[
https://jira.jboss.org/jira/browse/JBREM-918?page=com.atlassian.jira.plug...
]
David Lloyd commented on JBREM-918:
-----------------------------------
The problem is that then when a connection is broken, all state must be maintained for
some predetermined amount of time. This is a substantial amount of state - it can
encompass any number of clients and streams and even in-flight requests and replies which
may have been partially sent.
Perhaps this ties into graceful shutdown - if a connection is gracefully shutdown, then
all clients and connections are closed, otherwise the information is all kept?
Make "remote:" resilient against connection failure
---------------------------------------------------
Key: JBREM-918
URL:
https://jira.jboss.org/jira/browse/JBREM-918
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: r3 core: remote
Reporter: David Lloyd
Fix For: 3.1.0.Beta1
If a remote connection is dropped, it should be possible to re-establish the connection
and resume the session, without the loss of any in-flight requests/contexts/services/etc.
As a corollary, it might be worth exploring having more than one connection in a
"bundle" to help parallelize the transit load and avoid head-of-line bottleneck
problems. Perhaps it is worth looking into multihoming as well.
SSL contexts might be useful here.
--
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