[ https://jira.jboss.org/jira/browse/JBREM-918?page=com.atlassian.jira.plug... ] David Lloyd updated JBREM-918: ------------------------------ Summary: Make "remote:" resilient against connection failure (was: Make JRPP resilient against connection failure) Description: 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. was:If a JRPP 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. Note that this looks a lot like a list of features that SCTP already has... -- 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

[ 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? -- 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

[ https://jira.jboss.org/jira/browse/JBREM-918?page=com.atlassian.jira.plug... ] David Lloyd updated JBREM-918: ------------------------------ Fix Version/s: 3.1.0.Beta2 (was: 3.1.0.Beta1) -- 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

[ https://jira.jboss.org/jira/browse/JBREM-918?page=com.atlassian.jira.plug... ] David Lloyd updated JBREM-918: ------------------------------ Fix Version/s: 3.1.0.Beta3 (was: 3.1.0.Beta2) -- 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