[mule-user] Jms session should be transacted (MULE_ERROR-91304)

129 views
Skip to first unread message

pullareddy

unread,
Oct 13, 2011, 2:51:31 PM10/13/11
to us...@mule.codehaus.org
I am running into below exceptions when I am trying JMS transactions. I am sure that I am using the same JMS connector for the entire transaction scope.

I am using MULE CE 2.2.0 Build: 14110. Are there any known issues for JMS transactions with this build? Below is the complete log for each of the exceptions. Any clues? Thanks!

********************************************************************************
Message : Jms session should be transacted
Type : org.mule.transaction.IllegalTransactionStateException
Code : MULE_ERROR-91304
JavaDoc : http://www.mulesource.org/docs/site/current2/apidocs/org/mule/transaction/IllegalTransactionStateException.html
********************************************************************************

********************************************************************************
Message : Only a single resource can be bound to this type of transaction
Type : org.mule.transaction.IllegalTransactionStateException
Code : MULE_ERROR-91380
JavaDoc : http://www.mulesource.org/docs/site/current2/apidocs/org/mule/transaction/IllegalTransactionStateException.html
********************************************************************************

Log snapshots:

ERROR 2011-10-13 10:10:25,676 [DispatchThread: 1] org.mule.DefaultExceptionStrategy:
********************************************************************************
Message : Jms session should be transacted
Type : org.mule.transaction.IllegalTransactionStateException
Code : MULE_ERROR-91304
JavaDoc : http://www.mulesource.org/docs/site/current2/apidocs/org/mule/transaction/IllegalTransactionStateException.html
********************************************************************************
Exception stack is:
1. Jms session should be transacted (org.mule.transaction.IllegalTransactionStateException)
org.mule.transport.jms.JmsTransaction:44 (http://www.mulesource.org/docs/site/current2/apidocs/org/mule/transaction/IllegalTransactionStateException.html)
********************************************************************************
Root Exception stack trace:
org.mule.transaction.IllegalTransactionStateException: Jms session should be transacted
at org.mule.transport.jms.JmsTransaction.bindResource(JmsTransaction.java:44)
at org.mule.transport.jms.JmsConnector.getSession(JmsConnector.java:585)
at org.mule.transport.jms.JmsConnector.getSession(JmsConnector.java:558)
at org.mule.transport.jms.transformers.AbstractJmsTransformer.getSession(AbstractJmsTransformer.java:202)
at org.mule.transport.jms.transformers.AbstractJmsTransformer.transformToMessage(AbstractJmsTransformer.java:66)
at org.mule.transport.jms.transformers.ObjectToJMSMessage.transform(ObjectToJMSMessage.java:50)
at org.mule.transformer.AbstractMessageAwareTransformer.doTransform(AbstractMessageAwareTransformer.java:68)
at org.mule.transformer.AbstractTransformer.transform(AbstractTransformer.java:254)
at org.mule.DefaultMuleMessage.applyAllTransformers(DefaultMuleMessage.java:620)
at org.mule.DefaultMuleMessage.applyTransformers(DefaultMuleMessage.java:581)
at org.mule.DefaultMuleMessage.applyTransformers(DefaultMuleMessage.java:574)
at org.mule.transport.AbstractMessageReceiver$DefaultInternalMessageListener.onMessage(AbstractMessageReceiver.java:373)
at org.mule.transport.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:252)
at org.mule.transport.AbstractReceiverWorker$1.doInTransaction(AbstractReceiverWorker.java:114)
at org.mule.transaction.TransactionTemplate.execute(TransactionTemplate.java:99)
at org.mule.transport.AbstractReceiverWorker.doRun(AbstractReceiverWorker.java:131)
at org.mule.transport.AbstractReceiverWorker.run(AbstractReceiverWorker.java:62)
at org.mule.work.WorkerContext.run(WorkerContext.java:310)
at org.mule.work.SyncWorkExecutor.doExecute(SyncWorkExecutor.java:41)
at org.mule.work.MuleWorkManager.executeWork(MuleWorkManager.java:268)
at org.mule.work.MuleWorkManager.doWork(MuleWorkManager.java:156)
at org.mule.transport.jms.MultiConsumerJmsMessageReceiver$SubReceiver.onMessage(MultiConsumerJmsMessageReceiver.java:313)
at com.ibm.mq.jms.MQMessageConsumer$FacadeMessageListener.onMessage(MQMessageConsumer.java:399)
at com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl$JmsProviderMessageListener.onMessage(JmsMessageConsumerImpl.java:904)
at com.ibm.msg.client.wmq.internal.WMQAsyncConsumerShadow.honourNoLocal(WMQAsyncConsumerShadow.java:551)
at com.ibm.msg.client.wmq.internal.WMQAsyncConsumerShadow.consumer(WMQAsyncConsumerShadow.java:385)
at com.ibm.mq.jmqi.remote.internal.RemoteAsyncConsume.driveConsumer(RemoteAsyncConsume.java:1523)
at com.ibm.mq.jmqi.remote.internal.RemoteDispatchThread.run(RemoteDispatchThread.java:394)
at com.ibm.msg.client.commonservices.workqueue.WorkQueueItem.runTask(WorkQueueItem.java:209)
at com.ibm.msg.client.commonservices.workqueue.SimpleWorkQueueItem.runItem(SimpleWorkQueueItem.java:100)
at com.ibm.msg.client.commonservices.workqueue.WorkQueueItem.run(WorkQueueItem.java:224)
at com.ibm.msg.client.commonservices.workqueue.WorkQueueManager.runWorkQueueItem(WorkQueueManager.java:298)
at com.ibm.msg.client.commonservices.j2se.workqueue.WorkQueueManagerImplementation$ThreadPoolWorker.run(WorkQueueManagerImplementation.java:1220)

********************************************************************************

ERROR 2011-10-13 08:50:55,436 [DispatchThread: 1] org.mule.DefaultExceptionStrategy:
********************************************************************************
Message : Only a single resource can be bound to this type of transaction
Type : org.mule.transaction.IllegalTransactionStateException
Code : MULE_ERROR-91380
JavaDoc : http://www.mulesource.org/docs/site/current2/apidocs/org/mule/transaction/IllegalTransactionStateException.html
********************************************************************************
Exception stack is:
1. Only a single resource can be bound to this type of transaction (org.mule.transaction.IllegalTransactionStateException)
org.mule.transaction.AbstractSingleResourceTransaction:126 (http://www.mulesource.org/docs/site/current2/apidocs/org/mule/transaction/IllegalTransactionStateException.html)
********************************************************************************
Root Exception stack trace:
org.mule.transaction.IllegalTransactionStateException: Only a single resource can be bound to this type of transaction
at org.mule.transaction.AbstractSingleResourceTransaction.bindResource(AbstractSingleResourceTransaction.java:126)
at org.mule.transport.jms.JmsTransaction.bindResource(JmsTransaction.java:52)
at org.mule.transport.jms.JmsConnector.getSession(JmsConnector.java:585)
at org.mule.transport.jms.JmsConnector.getSession(JmsConnector.java:558)
at org.mule.transport.jms.transformers.AbstractJmsTransformer.getSession(AbstractJmsTransformer.java:202)
at org.mule.transport.jms.transformers.AbstractJmsTransformer.transformToMessage(AbstractJmsTransformer.java:66)
at org.mule.transport.jms.transformers.ObjectToJMSMessage.transform(ObjectToJMSMessage.java:50)
at org.mule.transformer.AbstractMessageAwareTransformer.doTransform(AbstractMessageAwareTransformer.java:68)
at org.mule.transformer.AbstractTransformer.transform(AbstractTransformer.java:254)
at org.mule.DefaultMuleMessage.applyAllTransformers(DefaultMuleMessage.java:620)
at org.mule.DefaultMuleMessage.applyTransformers(DefaultMuleMessage.java:581)
at org.mule.DefaultMuleMessage.applyTransformers(DefaultMuleMessage.java:574)
at org.mule.transport.AbstractMessageReceiver$DefaultInternalMessageListener.onMessage(AbstractMessageReceiver.java:373)
at org.mule.transport.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:252)
at org.mule.transport.AbstractReceiverWorker$1.doInTransaction(AbstractReceiverWorker.java:114)
at org.mule.transaction.TransactionTemplate.execute(TransactionTemplate.java:99)
at org.mule.transport.AbstractReceiverWorker.doRun(AbstractReceiverWorker.java:131)
at org.mule.transport.AbstractReceiverWorker.run(AbstractReceiverWorker.java:62)
at org.mule.work.WorkerContext.run(WorkerContext.java:310)
at org.mule.work.SyncWorkExecutor.doExecute(SyncWorkExecutor.java:41)
at org.mule.work.MuleWorkManager.executeWork(MuleWorkManager.java:268)
at org.mule.work.MuleWorkManager.doWork(MuleWorkManager.java:156)
at org.mule.transport.jms.MultiConsumerJmsMessageReceiver$SubReceiver.onMessage(MultiConsumerJmsMessageReceiver.java:313)
at com.ibm.mq.jms.MQMessageConsumer$FacadeMessageListener.onMessage(MQMessageConsumer.java:399)
at com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl$JmsProviderMessageListener.onMessage(JmsMessageConsumerImpl.java:904)
at com.ibm.msg.client.wmq.internal.WMQAsyncConsumerShadow.honourNoLocal(WMQAsyncConsumerShadow.java:551)
at com.ibm.msg.client.wmq.internal.WMQAsyncConsumerShadow.consumer(WMQAsyncConsumerShadow.java:385)
at com.ibm.mq.jmqi.remote.internal.RemoteAsyncConsume.driveConsumer(RemoteAsyncConsume.java:1523)
at com.ibm.mq.jmqi.remote.internal.RemoteDispatchThread.run(RemoteDispatchThread.java:394)
at com.ibm.msg.client.commonservices.workqueue.WorkQueueItem.runTask(WorkQueueItem.java:209)
at com.ibm.msg.client.commonservices.workqueue.SimpleWorkQueueItem.runItem(SimpleWorkQueueItem.java:100)
at com.ibm.msg.client.commonservices.workqueue.WorkQueueItem.run(WorkQueueItem.java:224)
at com.ibm.msg.client.commonservices.workqueue.WorkQueueManager.runWorkQueueItem(WorkQueueManager.java:298)
at com.ibm.msg.client.commonservices.j2se.workqueue.WorkQueueManagerImplementation$ThreadPoolWorker.run(WorkQueueManagerImplementation.java:1220)

********************************************************************************

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email


Pablo Kraan

unread,
Oct 13, 2011, 3:17:03 PM10/13/11
to us...@mule.codehaus.org

Mule 2.2.0 is really old, there were many fixes since that version was created, maybe you should try using 2.2.8 or the latest snapshot.

Pablo

pullareddy

unread,
Oct 13, 2011, 3:41:14 PM10/13/11
to us...@mule.codehaus.org
Thanks Pablo for your response! We will eventually be moving to the latest version of MULE but this is our current PROD version and have to live with it for some more time.
Reply all
Reply to author
Forward
0 new messages