• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

XA exception in JMS

 
Manon Baratt
Ranch Hand
Posts: 58
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I am getting this exception. My environment is WAS 7, Websphere MQ and Oracle. I would appreciate any explanation on why I am getting this exception.

Thanks!!!

An exception occurred while invoking end on an XA Resource Adapter from DataSource JMS$SchedulerQCF$JMSManagedConnection@3, within transaction ID {XidImpl: formatId(57415344), gtrid_length(36), bqual_length(54),
data(000001360622f7a30000000100000053401e9b9dff66f138972edc04e7f8987765b1d945000001360622f7a30000000100000053401e9b9dff66f138972edc04e7f8987765b1d945000000010000000000000000000000000003)} : javax.transaction.xa.XAException: The method 'xa_end' has failed with errorCode '100'.
at com.ibm.mq.jmqi.JmqiXAResource.end(JmqiXAResource.java:457)
at com.ibm.ejs.jms.JMSManagedSession$JMSXAResource.end(JMSManagedSession.java:1649)
at com.ibm.ejs.j2c.XATransactionWrapper.end(XATransactionWrapper.java:603)
at com.ibm.ws.Transaction.JTA.JTAResourceBase.end(JTAResourceBase.java:240)
at com.ibm.tx.jta.RegisteredResources.sendEnd(RegisteredResources.java:1108)
at com.ibm.tx.jta.RegisteredResources.distributeEnd(RegisteredResources.java:1082)
at com.ibm.tx.jta.TransactionImpl.distributeEnd(TransactionImpl.java:1726)
at com.ibm.tx.jta.TransactionImpl.prepareResources(TransactionImpl.java:1423)
at com.ibm.ws.tx.jta.TransactionImpl.stage1CommitProcessing(TransactionImpl.java:556)
at com.ibm.tx.jta.TransactionImpl.processCommit(TransactionImpl.java:985)
at com.ibm.tx.jta.TransactionImpl.commit(TransactionImpl.java:919)
at com.ibm.ws.tx.jta.TranManagerImpl.commit(TranManagerImpl.java:436)
at com.ibm.tx.jta.TranManagerSet.commit(TranManagerSet.java:161)
at com.ibm.ejs.csi.TranStrategy.commit(TranStrategy.java:927)
at com.ibm.ejs.csi.TranStrategy.postInvoke(TranStrategy.java:230)
at com.ibm.ejs.csi.TransactionControlImpl.postInvoke(TransactionControlImpl.java:570)
at com.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.java:4558)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:111)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:136)
at com.ibm.ejs.jms.listener.ServerSession.run(ServerSession.java:567)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)
 
E Armitage
Rancher
Posts: 989
9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sounds like Aged timeout issue. Try setting Aged Timeout property to zero in your WAS connection pool settings
as explained here:http://www-01.ibm.com/support/docview.wss?uid=swg21508472
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic