If you are using MDBs then deploy the them in deploy-hasingleton
instead of deploy.
We are deploying our MDBs under the deploy-hasingleton. If we try to deploy all the cluster nodes with the mdb-client-id's all being the same we receive the following exception :
2007-06-28 10:31:51,958 ERROR [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Reconnect failed: JMS provider failure detected for InvestmentBalanceLookup
org.jboss.deployment.DeploymentException: Error during topic setup; - nested throwable: (javax.jms.InvalidClientIDException: This client id 'CCDurablesIBL' is already registered!)
Caused by: javax.jms.InvalidClientIDException: This client id 'CCDurablesIBL' is already registered!
which caused us to use different mdb-client-id's across the cluster. I think the multiple entries in the jms_subscriptions tables is what is causing the other nodes in the cluster to pick up and process the messages.