JBossMessaging JMS clustering failover for clean server shutdown in JBoss EAP 5
Issue
- When one node is shutdown we see the following errors in the logs
ERROR [org.jboss.jms.client.FailoverCommandCenter] (Thread-39) Failover failed
javax.jms.JMSException: Cannot find a cached connection factory delegate for node -1
at org.jboss.jms.client.container.ClusteringAspect.handleCreateConnectionDelegate(ClusteringAspect.java:217)
...
at org.jboss.remoting.ConnectionValidator$3.run(ConnectionValidator.java:524)
ERROR [org.jboss.jms.client.container.ClientConsumer] (Thread-39) ClientConsumer[x3-kpua2h1h-
1-ier92h1h-neusmf-i5o62a] The connection is about to be aborted, stop the blocking receiving.
ERROR [org.jboss.jms.client.container.ConnectionFailureListener] (Thread-39) Caught exception
in handling failure
javax.jms.JMSException: Cannot find a cached connection factory delegate for node -1
at org.jboss.jms.client.container.ClusteringAspect.handleCreateConnectionDelegate(ClusteringAspect.java:217)
...
at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:84)
- The following attribute is set to false in *-persistence-service.xml. What are its impacts?
<!-- Set this to true if you want failover of connections to occur when a node is shut down -->
<attribute name="FailoverOnNodeLeave">false</attribute>
- Our expectation is that whenever a node is shutdown all jms functions should failover to the other nodes that are up and running. And once the other node is back up it should join and form the cluster just like it did prior to shutdown.
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 5.x
- JBoss Enterprise SOA Platform (SOA-P)
- 5.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.