[
https://jira.jboss.org/jira/browse/JBREM-918?page=com.atlassian.jira.plug...
]
Trustin Lee commented on JBREM-918:
-----------------------------------
Even if the connection was shut down gracefully, the client might want to connect again?
We could simply keep the information for about 30 sec for example regardless if it is a
graceful shutdown.
+1 for dropping the in-flight requests with a distinguishable exception.
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.Beta2
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