[ https://jira.jboss.org/jira/browse/JBMESSAGING-1732?page=com.atlassian.ji... ] Howard Gao commented on JBMESSAGING-1732: ----------------------------------------- Here is how i want to fix it: On creation of each remote connection, register an ExceptionListener. The listener's onException() method will be called if the connection has a problem. In onException(), first suspend all suckers that associated with this connection and then stop the connection. Suspending suckers means we stop and close the cosumer, but we don't stop the producer, because the producer is always local. Then we start to retry the connection. We provide two parameters in messaging-service.xml, one is retry times (default -1, means retry forever), the other is retry interval (millis). Once retry successful, we resume the suckers, meaning we use the new session to create new consumers and restore the consuming state of the suckers. -- 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