We have a fairly large and complex application running in a production environment. When JBoss occationally is killed while running an JMS transaction, for whatever reasons, the application some times wont start when JBoss is restarted.
See error message below.
To overcome the problem we figured out that we have to do the following:
1. Stop JBoss
2. flush out some temp directories manually: server/default/tmp and server/default/data (hypersonix queue persistence I guess) as well as the .ear file
3. Start JBoss and redeploy the application
This is a bit irritating. Is it something that can be handled more gracefully, or even something that can be fixed in a future version?
ERRORMESSAGE:
==============
2003-08-01 18:06:23,573 WARN [org.jboss.ejb.plugins.jms.JMSContainerInvoker] 2003-08-01 18:06:23,573JMS provider failure detected:
javax.jms.JMSException: Error creating the dlq connection: XAConnectionFactory not bound
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:152)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:158)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:394)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:579)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.onException(JMSContainerInvoker.java:1079)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$1.run(JMSContainerInvoker.java:591)
