Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-9950

one-off JBPAPP-9758 - Shunned node is restarting JBM even when it's still disconnected from network

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • Messaging
    • None
    • Hide
      When MessagingClusterHealthMBean is used to stop JBM component when node is disconnected from cluster and database then attributes check-valid-connection-sql and valid-connection-checker-class-name should be set in *-ds.xml to detect corrupted database connections.
      Show
      When MessagingClusterHealthMBean is used to stop JBM component when node is disconnected from cluster and database then attributes check-valid-connection-sql and valid-connection-checker-class-name should be set in *-ds.xml to detect corrupted database connections.
    • Not Yet Documented
    • NEW 

      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:

        1. configuration-node-A.zip
          234 kB

              gaohoward Howard Gao
              mnovak1@redhat.com Miroslav Novak
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: