|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
time out problem |
« View previous topic :: View next topic » |
Author |
Message
|
rohit_ison |
Posted: Wed Jan 23, 2008 2:50 am Post subject: time out problem |
|
|
Newbie
Joined: 23 Jan 2008 Posts: 4
|
Hi
I am getting following exception in our application while trying to put a message in MQ.
Can anyone please help me out.
[1/22/08 23:59:31:271 CST] 0000001f TimeoutManage I WTRN0006W: Transaction 00000117A538FE04000000010000000C77939D1E5AE0A110C4A43A9110DAC0021DCDD2CD00000117A538FE04000000010000000C77939D1E5AE0A110C4A43A9110DAC0021DCDD2CD00000001 has timed out after 120 seconds.
Thanks,
- Rohit. |
|
Back to top |
|
 |
Vitor |
Posted: Wed Jan 23, 2008 3:32 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
How have you determined this is an MQ problem?
Looks more like another component or the transaction coordinator is timing out to me. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
rohit_ison |
Posted: Wed Jan 23, 2008 10:08 pm Post subject: time out problem |
|
|
Newbie
Joined: 23 Jan 2008 Posts: 4
|
I am not sure waht exactly it is..
But yes as soon as I try to put the message in MQ, the transaction rolls back an I get following exception...
If anyone has faced same problem please throw some light..
Following is the detailed error I am getting.
[1/22/08 23:59:31:271 CST] 0000001f TimeoutManage I WTRN0006W: Transaction 00000117A538FE04000000010000000C77939D1E5AE0A110C4A43A9110DAC0021DCDD2CD00000117A538FE04000000010000000C77939D1E5AE0A110C4A43A9110DAC0021DCDD2CD00000001 has timed out after 120 seconds.
[1/23/08 0:00:13:148 CST] 0000002e XATransaction E J2CA0026E: Method addSync caught javax.transaction.RollbackException: Transaction rolled back
at com.ibm.ws.Transaction.JTA.TransactionImpl.registerSynchronization(TransactionImpl.java:3490)
at com.ibm.ws.Transaction.JTA.TransactionImpl.registerSynchronization(TransactionImpl.java:3469)
at com.ibm.ws.Transaction.JTA.TranManagerSet.registerSynchronization(TranManagerSet.java:484)
at com.ibm.ejs.j2c.XATransactionWrapper.addSync(XATransactionWrapper.java:284)
at com.ibm.ejs.j2c.ConnectionManager.initializeForUOW(ConnectionManager.java:1342)
at com.ibm.ejs.j2c.ConnectionManager.involveMCInTran(ConnectionManager.java:1085)
at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:628)
at com.ibm.ejs.jms.JMSQueueConnectionHandle.createQueueSession(JMSQueueConnectionHandle.java:176)
at clyde.jms.util.ClydeJMSUtil.createSession(Unknown Source)
at clyde.jms.cap.ClydeJMSClientAccessProxy.primeRequest(Unknown Source)
at clyde.jms.cap.ClydeJMSClientAccessProxy.primeRequest(Unknown Source)
at clyde.jms.cap.ClydeJMSClientAccessProxy.executeRequest(Unknown Source)
at com.nm.techservice.autotkt.cap.createupdateticket.CreateTicketCAP.sendTicketToQueue(Unknown Source)
at com.nm.techservice.autotkt.cap.createupdateticket.CreateTicketCAP.sendNewTicketToQueue(Unknown Source)
at com.nm.techservice.autotkt.pab.autoticket.AutoTicketPAB.handleCreateNewTicket(Unknown Source)
at com.nm.techservice.autotkt.pab.autoticket.AutoTicketPAB.processEvent(Unknown Source)
at com.nm.techservice.autotkt.mdb.processevent.ProcessEventMDB.handleTextRequest(Unknown Source)
at clyde.mb.base.AbstractTextMessageBean.onMessage(Unknown Source)
at clyde.mb.base.AbstractMessageBean.routeToAppropriateOnMessage(Unknown Source)
at clyde.mb.base.AbstractMessageBean.onMessage(Unknown Source)
at com.ibm.ejs.jms.listener.MDBWrapper$PriviledgedOnMessage.run(MDBWrapper.java:319)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java(Compiled Code))
at com.ibm.ejs.jms.listener.MDBWrapper.callOnMessage(MDBWrapper.java:288)
at com.ibm.ejs.jms.listener.MDBWrapper.onMessage(MDBWrapper.java:266)
at com.ibm.mq.jms.MQSession.run(MQSession.java:1593)
at com.ibm.ejs.jms.JMSSessionHandle.run(JMSSessionHandle.java:968)
at com.ibm.ejs.jms.listener.ServerSession.connectionConsumerOnMessage(ServerSession.java:862)
at com.ibm.ejs.jms.listener.ServerSession.onMessage(ServerSession.java:627)
at com.ibm.ejs.jms.listener.ServerSession.dispatch(ServerSession.java:594)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:5
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
at com.ibm.ejs.jms.listener.ServerSessionDispatcher.dispatch(ServerSessionDispatcher.java:37)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:91)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:127)
at com.ibm.ejs.jms.listener.ServerSession.run(ServerSession.java:479)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
while trying to register the Resource Adapter with the Synchronization Manager for the current transaction, and threw a ResourceException.
[1/23/08 0:00:15:036 CST] 0000002e ServerSession W WMSG0031E: Exception processing JMS Message for MDB ProcessEventMDB, JMSDestination jms/AutoTicketRequestQueue : javax.ejb.TransactionRolledbackLocalException: ; nested exception is: com.ibm.websphere.csi.CSITransactionRolledbackException: Transaction marked rollbackonly
com.ibm.websphere.csi.CSITransactionRolledbackException: Transaction marked rollbackonly
at com.ibm.ejs.csi.TranStrategy.postInvoke(TranStrategy.java:174)
at com.ibm.ejs.csi.TransactionControlImpl.postInvoke(TransactionControlImpl.java:579)
at com.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.java:3886)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:102)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:127)
at com.ibm.ejs.jms.listener.ServerSession.run(ServerSession.java:479)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
javax.ejb.TransactionRolledbackLocalException: ; nested exception is: com.ibm.websphere.csi.CSITransactionRolledbackException: Transaction marked rollbackonly
at com.ibm.ejs.csi.TranStrategy.postInvoke(TranStrategy.java:174)
at com.ibm.ejs.csi.TransactionControlImpl.postInvoke(TransactionControlImpl.java:579)
at com.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.java:3886)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:102)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:127)
at com.ibm.ejs.jms.listener.ServerSession.run(ServerSession.java:479)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
Thanks,
- Rohit |
|
Back to top |
|
 |
Vitor |
Posted: Fri Jan 25, 2008 4:03 pm Post subject: Re: time out problem |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
rohit_ison wrote: |
I am not sure waht exactly it is..
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
while trying to register the Resource Adapter with the Synchronization Manager for the current transaction, and threw a ResourceException.
|
I'd say it was exactly that.
I'd look at your resource coordinator gneerally, and the XA configuration specifically. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|