Clustered ConnectionFactory bound twice on a failover event (and the first time is an inconsistent state) --------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-720 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-720 Project: JBoss Messaging Issue Type: Sub-task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta2 21:49:59,515 DEBUG @SocketServerInvokerThread-127.0.0.1-0 [ServerConnectionFactoryEndpoint] ConnectionFactoryEndpoint[1] received client-side failover request. Creating failover connection to replace connection to failed node 1 21:49:59,515 INFO @SocketServerInvokerThread-127.0.0.1-0 [ServerPeer] ServerPeer[0] waiting for server-side failover for failed node 1 to complete 21:49:59,515 DEBUG @SocketServerInvokerThread-127.0.0.1-0 [ServerPeer] ServerPeer[0] blocking on the failover lock, waiting for failover to start 21:49:59,625 INFO @Thread-3 [DefaultClusteredPostOffice] ClusteredPostOffice[0:Clustered JMS:127.0.0.1:1406] got new view: [127.0.0.1:1406|2] [127.0.0.1:1406] 21:49:59,640 DEBUG @Thread-3 [DefaultClusteredPostOffice] ClusteredPostOffice[0:Clustered JMS:127.0.0.1:1406]: 127.0.0.1:1423 left 21:49:59,640 DEBUG @Thread-3 [DefaultClusteredPostOffice] ClusteredPostOffice[0:Clustered JMS:127.0.0.1:1406]: node 1 has crashed 21:49:59,640 TRACE @Thread-3 [DefaultClusteredPostOffice] ClusteredPostOffice[0:Clustered JMS:127.0.0.1:1406] checking for any stranded transactions for node 1 21:49:59,640 TRACE @Thread-3 [DefaultClusteredPostOffice] ClusteredPostOffice[0:Clustered JMS:127.0.0.1:1406] transaction check complete 21:49:59,640 DEBUG @Thread-3 [DefaultClusteredPostOffice] ClusteredPostOffice[0:Clustered JMS:127.0.0.1:1406] cleaning local data for node 1 21:49:59,640 DEBUG @Thread-3 [DefaultClusteredPostOffice] ClusteredPostOffice[0:Clustered JMS:127.0.0.1:1406] received ADDRESS_INFO replication change from node 1: {0=[synch addr 127.0.0.1:1406, asynch addr 127.0.0.1:1409]} 21:49:59,640 DEBUG @Thread-3 [DefaultClusteredPostOffice] Cluster map: 0->[synch addr 127.0.0.1:1406, asynch addr 127.0.0.1:1409] 21:49:59,640 DEBUG @Thread-3 [DefaultClusteredPostOffice] Failover map: 0->0 21:49:59,640 DEBUG @Thread-3 [ConnectionFactoryJNDIMapper] Server[0].ConnFactoryJNDIMapper received ADDRESS_INFO replication change from node 1: {0=[synch addr 127.0.0.1:1406, asynch addr 127.0.0.1:1409]} 21:49:59,640 DEBUG @Thread-3 [ConnectionFactoryJNDIMapper] Server[0].ConnFactoryJNDIMapper received address mapping change {0=[synch addr 127.0.0.1:1406, asynch addr 127.0.0.1:1409]} 21:49:59,640 DEBUG @Thread-3 [ConnectionFactoryJNDIMapper] Server[0].ConnFactoryJNDIMapper rebinding JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={0,1}] as /ConnectionFactory 21:49:59,640 DEBUG @Thread-3 [ConnectionFactoryJNDIMapper] Server[0].ConnFactoryJNDIMapper rebinding JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={0,1}] as /XAConnectionFactory 21:49:59,640 DEBUG @Thread-3 [ConnectionFactoryJNDIMapper] Server[0].ConnFactoryJNDIMapper rebinding JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={0,1}] as java:/ConnectionFactory 21:49:59,640 DEBUG @Thread-3 [ConnectionFactoryJNDIMapper] Server[0].ConnFactoryJNDIMapper rebinding JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={0,1}] as java:/XAConnectionFactory -- 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