[ http://jira.jboss.com/jira/browse/JBMESSAGING-885?page=all ] Ben Anderson updated JBMESSAGING-885: ------------------------------------- Attachment: MultipleServerReconnectTest.java I've developed a new test case that creates a message producer and consumer on two separate JBoss Messaging servers. By continually shutting down and restarting each JBoss Messaging server I can eventually cause the shutting down of one server to stop the message listeners on the *other* server. This test case also demonstrates the same reconnection issue that I've raised in this post http://www.jboss.org/index.html?module=bb&op=viewtopic&t=102233 Our JBoss Messaging servers have different ServerPeerIDs and StoreIds as suggested elsewhere. To run the test case, start both JBoss Messaging servers then start the test case. A producer will be created on each server and will start dispatching messages to a queue. A message listener on the queue will acknowledge the dispatched message. Stop one of the servers for a while then restart it. The producer and consumer on that server should start up again. Quite often they do not. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBMESSAGING-885?page=all ] Tim Fox updated JBMESSAGING-885: -------------------------------- Assignee: (was: Ovidiu Feodorov) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBMESSAGING-885?page=all ] Tim Fox closed JBMESSAGING-885. ------------------------------- Resolution: Done After upgrading to remoting 2.2.0.SP1, implementing the callback failure deadlock fix, I do not see this problem, so assuming is fixed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira