JBossMQ errors after starting up with many messages in the q
Using JBoss 4.0.5, when I startup my application with ~2400 messages already persisted (but not yet processed) in the queue the application server correctly starts to dispatch the messages.
The problem is that I get some (~4-10) errors like the following, when the execution finishes I see the same amount of unprocessed messages in the database.
2006-12-04 16:51:46,651 ERROR [org.jboss.jms.asf.StdServerSession] (JMS SessionPool Worker-5) failed to commit/rollback
org.jboss.mq.SpyXAException: Resource manager error during commit; - nested throwable: (javax.jms.JMSException: Transaction is not active for rollback)
at org.jboss.mq.SpyXAException.getAsXAException(SpyXAException.java:72)
at org.jboss.mq.SpyXAResource.commit(SpyXAResource.java:92)
at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:317)
at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:905)
at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:170)
at org.jboss.mq.SpySession.run(SpySession.java:323)
at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:194)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.jms.JMSException: Transaction is not active for rollback
at org.jboss.mq.pm.Tx.rollback(Tx.java:253)
at org.jboss.mq.pm.TxManager.rollbackTx(TxManager.java:180)
at org.jboss.mq.server.JMSDestinationManager.transact(JMSDestinationManager.java:449)
at org.jboss.mq.server.JMSServerInterceptorSupport.transact(JMSServerInterceptorSupport.java:126)
at org.jboss.mq.security.ServerSecurityInterceptor.transact(ServerSecurityInterceptor.java:197)
at org.jboss.mq.server.TracingInterceptor.transact(TracingInterceptor.java:352)
at org.jboss.mq.server.JMSServerInvoker.transact(JMSServerInvoker.java:132)
at org.jboss.mq.il.jvm.JVMServerIL.transact(JVMServerIL.java:175)
at org.jboss.mq.Connection.send(Connection.java:1110)
at org.jboss.mq.SpyXAResourceManager.commit(SpyXAResourceManager.java:166)
at org.jboss.mq.SpyXAResource.commit(SpyXAResource.java:88)
... 7 more
I have configured JBOSSMQ to use the MS SQL Server 2005 to persist the message queue.
Any ideas on how can I solve this?