[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-429) HA-JMS + MDB problem: MDB Container not reconnecting properly.

[ http://jira.jboss.com/jira/browse/EJBTHREE-429?page=comments#action_12342118 ] Darran Lofthouse commented on EJBTHREE-429: ------------------------------------------- The exceptions fixed by this bug are: - org.jboss.mq.SpyJMSException: Cannot disable the connection with the JMS server; - nested throwable: (java.io.IOException: Client is not connected) at org.jboss.mq.SpyJMSException.getAsJMSException(SpyJMSException.java:66) at org.jboss.mq.SpyJMSException.rethrowAsJMSException(SpyJMSException.java:51) at org.jboss.mq.Connection.doStop(Connection.java:1235) at org.jboss.mq.Connection.stop(Connection.java:696) at org.jboss.ejb3.mdb.DLQHandler.stopService(DLQHandler.java:171) at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:300) at org.jboss.system.ServiceMBeanSupport.stop(ServiceMBeanSupport.java:191) at org.jboss.system.ServiceMBeanSupport.jbossInternalDestroy(ServiceMBeanSupport.java:323) at org.jboss.system.ServiceMBeanSupport.destroy(ServiceMBeanSupport.java:206) at org.jboss.ejb3.mdb.MDB.destroy(MDB.java:1102) at org.jboss.ejb3.mdb.MDB$ExceptionListenerImpl.onException(MDB.java:1225) at org.jboss.mq.Connection$ExceptionListenerRunnable.run(Connection.java:1366) at java.lang.Thread.run(Thread.java:595) Caused by: java.io.IOException: Client is not connected at org.jboss.mq.il.uil2.SocketManager.internalSendMessage(SocketManager.java:238) at org.jboss.mq.il.uil2.SocketManager.sendMessage(SocketManager.java:206) at org.jboss.mq.il.uil2.UILServerIL.setEnabled(UILServerIL.java:197) at org.jboss.mq.Connection.doStop(Connection.java:1231) ... 10 more javax.naming.NamingException: Could not bind user transaction for ejb name ReportGenerationMDB into JNDI under jndiName: /UserTransaction [Root exception is javax.naming.NameAlreadyBoundException] at org.jboss.ejb3.EJBContainer.resolveInjectors(EJBContainer.java:641) at org.jboss.ejb3.EJBContainer.initializePool(EJBContainer.java:586) at org.jboss.ejb3.EJBContainer.start(EJBContainer.java:518) at org.jboss.ejb3.mdb.MDB.start(MDB.java:247) at org.jboss.ejb3.mdb.MDB$ExceptionListenerImpl.onException(MDB.java:1226) at org.jboss.mq.Connection$ExceptionListenerRunnable.run(Connection.java:1366) at java.lang.Thread.run(Thread.java:595) Caused by: javax.naming.NameAlreadyBoundException at org.jnp.server.NamingServer.bind(NamingServer.java:129) at org.jnp.interfaces.NamingContext.bind(NamingContext.java:551) at org.jnp.interfaces.NamingContext.bind(NamingContext.java:516) at org.jboss.util.naming.Util.bind(Util.java:87) at org.jboss.util.naming.Util.bind(Util.java:74) at org.jboss.ejb3.EJBContainer.resolveInjectors(EJBContainer.java:638) ... 6 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira