I am attempting to setup a JBoss cluster using HAJNDI and a single JMS Queue deployed in deploy-hasingleton.
I am using JBoss 4.0.1sp1 on Linux. Oracle is the JMS StateManager My initial question is: If I am running multiple servers on the same machine and utilizing the bindings.xml file, does the JNDI port (typically 1100) need to be the same or different for all 3 servers? Currently set at 1100, 1200, 1300 respectively. Given that setup, everything works great until I shutdown the first server (JNDI port 1100) to test the HAJNDI and HASingleton Failover. The remaining servers throw the following stack trace: 2005-03-02 14:04:28,675 ERROR [org.jboss.ejb.plugins.jms.DLQHandler] Initialization failed DLQHandler | javax.jms.JMSException: Error creating the dlq connection: XAConnectionFactory not bound | at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:166) | at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:238) | at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:165) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:557) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:813) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.run(JMSContainerInvoker.java:1323) | at java.lang.Thread.run(Thread.java:534) | 2005-03-02 14:04:28,678 DEBUG [org.jboss.ha.framework.server.HAPartitionImpl] responses: [sender=beretta:33431 (additional data: 17 bytes), retval=null, received=true, suspected=false] | | 2005-03-02 14:04:28,684 WARN [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] javax.naming.NameNotFoundException: XAConnectionFactory not bound | 2005-03-02 14:04:28,712 WARN [org.jboss.ejb.plugins.jms.JMSContainerInvoker] JMS provider failure detected: | javax.jms.JMSException: Error creating the dlq connection: XAConnectionFactory not bound | at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:166) | at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:238) | at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:165) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:557) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:813) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.run(JMSContainerInvoker.java:1323) | at java.lang.Thread.run(Thread.java:534) | 2005-03-02 14:04:28,713 ERROR [org.jboss.ejb.plugins.jms.DLQHandler] Initialization failed DLQHandler | javax.jms.JMSException: Error creating the dlq connection: XAConnectionFactory not bound | at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:166) | at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:238) | at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:165) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:557) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:813) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.run(JMSContainerInvoker.java:1323) | at java.lang.Thread.run(Thread.java:534) | 2005-03-02 14:04:28,718 WARN [org.jboss.ejb.plugins.jms.JMSContainerInvoker] JMS provider failure detected: | javax.jms.JMSException: Error creating the dlq connection: XAConnectionFactory not bound | at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:166) | at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:238) | at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:165) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:557) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:813) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.run(JMSContainerInvoker.java:1323) | at java.lang.Thread.run(Thread.java:534) | Once the first server is brought back up,it throws this stack trace over and over again: | 2005-03-02 14:13:21,962 INFO [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Trying to reconnect to JMS provider | 2005-03-02 14:13:21,970 WARN [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] javax.naming.NameNotFoundException: XAConnectionFactory not bound | 2005-03-02 14:13:31,964 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Destroying DLQHandler | 2005-03-02 14:13:31,964 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Destroyed DLQHandler | 2005-03-02 14:13:31,964 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Initializing | 2005-03-02 14:13:31,965 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Looking up provider adapter: java:/DefaultJMSProvider | 2005-03-02 14:13:31,965 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Provider adapter: [EMAIL PROTECTED] | 2005-03-02 14:13:31,965 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Creating DLQHandler | 2005-03-02 14:13:31,966 DEBUG [org.jboss.ha.framework.server.HAPartitionImpl] dests=[beretta:33425 (additional data: 17 bytes)], method_call=HAJNDI.lookupLocally(XAConnectionFactory), mode=2, timeout=60000 | 2005-03-02 14:13:31,966 DEBUG [org.jboss.ha.framework.server.HAPartitionImpl] real_dests=[beretta:33425 (additional data: 17 bytes)] | 2005-03-02 14:13:31,974 DEBUG [org.jboss.ha.framework.server.HAPartitionImpl] responses: [sender=beretta:33425 (additional data: 17 bytes), retval=null, received=true, suspected=false] | | 2005-03-02 14:13:31,975 ERROR [org.jboss.ejb.plugins.jms.DLQHandler] Initialization failed DLQHandler | javax.jms.JMSException: Error creating the dlq connection: XAConnectionFactory not bound | at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:166) | at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:238) | at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:165) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:557) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:813) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.run(JMSContainerInvoker.java:1323) | at java.lang.Thread.run(Thread.java:534) | 2005-03-02 14:13:31,975 WARN [org.jboss.ejb.plugins.jms.JMSContainerInvoker] JMS provider failure detected: | javax.jms.JMSException: Error creating the dlq connection: XAConnectionFactory not bound | at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:166) | at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:238) | at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:165) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:557) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:813) | at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.run(JMSContainerInvoker.java:1323) | at java.lang.Thread.run(Thread.java:534) | 2005-03-02 14:13:31,981 INFO [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Reconnected to JMS provider | So with the exception of the port numbers, the deploy-hasingleton directory is the same on all servers. What do I need to do for failover to work and recover correctly? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3868542#3868542 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3868542 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
