[ https://jira.jboss.org/jira/browse/JGRP-1200?page=com.atlassian.jira.plug... ] Bela Ban commented on JGRP-1200: -------------------------------- I believe the underlying cause may be the fact that the reconnector in TCPGOSSIP always tries to reconnect *all* stubs, not just the ones which are currently disconnected. We could simply fix this by checking in RouterStub.connect() whether we're already connected and - is yes - simply return from connect(). However, there is another problem: when out of {A, B, C}, B and C are disconnected, and suddenly the reconnector successfully connects to B, then the reconnector will get stopped, and won't even try to connect to C ! I think we should change both the reconnector and the connection checker to only reconnect to disconnected stubs (reconnector) and to only check the connection health (connection checker) for connected stubs. I propose that both reconnector and connection checker have a list of stubs that we can remove from or add to. When the list is empty, the task is stopped. This issue causes me problems in my JBossWorld demo, so I need to fix this this week. -- 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/JGRP-1200?page=com.atlassian.jira.plug... ] Bela Ban resolved JGRP-1200. ---------------------------- Resolution: Done Your change to RouterStubManager fixed both problems ! I verified that connecting to B works when A is down, plus there are no leftover registrations. Resolving this issue... -- 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