Details
-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
-
Not Yet Documented
-
NEW
Description
1. Start cluster of 2 nodes - node A and node B - each node has deployed clustered topic "topic/InTopic" - each node has deployed non-clustered queue "queue/OutQueue" 2. Deploy MDB to each node - mdb receives messages from InTopic, creates new message and send it to OutQueue - each mdb creates durable subscription with unique clientId and subscriptionName 3. Disconnect node A from cluster and database at the same time 4. Wait until JBM component stops on node A (more than 2*NodeStateRefreshInterval) 5. Still wait and see that node A is trying to restart JBM component which fails
Logs (too big to be attached here) dowload using command:
scp messaging-20.jbm.lab.bos.redhat.com:/home/mnovak/logs.zip .
Exception:
14:26:06,052 INFO [ServerPeer] JMS ServerPeer[1] stopped 14:26:06,057 INFO [MessagingClusterHealthMBean] JBM node is stopped. 14:26:09,280 ERROR [ClusterConnectionManager] Retrying ConnectionInfo org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager$ConnectionInfo@17f7ed6e failed after maxmum retry: 8 14:27:06,058 INFO [MessagingClusterHealthMBean] Restarting JBM node... // this should not happen - node A is still disconnected 14:27:11,117 WARN [TxConnectionManager] Connection error occured: org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@57525d9f[state=NORMAL mc=org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@60809e82 handles=1 lastUse=1347452766058 permit=true trackByTx=true mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@498281f1 context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@4fd2ac36 xaResource=org.jboss.resource.connectionmanager.TxConnectionManager$LocalXAResource@1c269a4d txSync=null] com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception:
