[jboss-user] [JBoss Messaging] - Weird transaction error
TheOverlord
do-not-reply at jboss.com
Fri Aug 8 03:37:14 EDT 2008
I'm getting these strange transaction related errors from an MDB consuming messages from queue:
| 2008-08-07 18:22:42,414 [JMS SessionPool Worker-5] WARN com.arjuna.ats.jta.logging.loggerI18N - [com.arjuna.ats.internal.jta.resources.arjunacore.preparefailed] [com.arjuna.ats.internal.jta.resources.arjunacore.preparefailed] XAResourceRecord.prepare - prepare failed with exception java.lang.IllegalMonitorStateException
| 2008-08-07 18:22:42,414 [JMS SessionPool Worker-5] WARN com.arjuna.ats.arjuna.logging.arjLoggerI18N - [com.arjuna.ats.arjuna.coordinator.BasicAction_36] - BasicAction.End() - prepare phase of action-id -53eef977:b8fd:489b9f66:dea failed.
| 2008-08-07 18:22:42,414 [JMS SessionPool Worker-5] WARN com.arjuna.ats.arjuna.logging.arjLoggerI18N - [com.arjuna.ats.arjuna.coordinator.BasicAction_38] - Action Aborting
| 2008-08-07 18:22:42,419 [JMS SessionPool Worker-5] ERROR org.jboss.jms.asf.StdServerSession - failed to commit/rollback
| javax.transaction.RollbackException: [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] Can't commit because the transaction is in aborted state
| at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1394)
| at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135)
| at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:87)
| at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:351)
| at org.jboss.jms.client.container.ClientConsumer.callOnMessage(ClientConsumer.java:160)
| at org.jboss.jms.client.container.SessionAspect.handleRun(SessionAspect.java:831)
| at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect14.invoke(SessionAspect14.java)
| at org.jboss.jms.client.delegate.ClientSessionDelegate$run_N8003352271541955702.invokeNext(ClientSessionDelegate$run_N8003352271541955702.java)
| at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
| at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
| at org.jboss.jms.client.delegate.ClientSessionDelegate$run_N8003352271541955702.invokeNext(ClientSessionDelegate$run_N8003352271541955702.java)
| at org.jboss.jms.client.delegate.ClientSessionDelegate.run(ClientSessionDelegate.java)
| at org.jboss.jms.client.JBossSession.run(JBossSession.java:199)
| at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:194)
|
I've already opened a support ticket on this but I just wanted to know what you think about this.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169483#4169483
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169483
More information about the jboss-user
mailing list