| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ Session -- Timeouts? |
« View previous topic :: View next topic » |
| Author |
Message
|
| sley |
 Posted: Tue Oct 22, 2002 6:58 am Post subject: MQ Session -- Timeouts? |
 |
|
Novice
Joined: 18 Dec 2001
Posts: 11
|
Hi.
Our application currently receives the message off the queue using the onMessage() method and sends it off for processing. Within the onMessage() method, a transaction is started and once the process is complete, the transaction is committed.
However, sometimes the process takes around 2-3 hours to complete (we're working on the performance now  ). When the process is complete and control returns to the onMessage() method, it tries to commit but instead we get the following jms exception.
Is there a timeout for sessions? I don't recall seeing on in the jms api.
thanks.
Sley
Error occurred while receiving a message: javax.jms.TransactionRolledBackException: MQJMS0011: Call to Session.commit resulted in a rollback of the current transaction
javax.jms.TransactionRolledBackException: MQJMS0011: Call to Session.commit resulted in a rollback of the current transaction
at com.ibm.mq.jms.MQQueueSession.commit(MQQueueSession.java:389)
at com.ml.edsi.mif.msgreceiver.MIFQueueReceiverThread.onMessage(MIFQueueReceiverThread.java:104)
at com.ibm.mq.jms.MQQueueReceiver.receiveAsync(MQQueueReceiver.java:639)
at com.ibm.mq.jms.contact admin.run(contact admin.java:355)
edsiorad1% ^C |
|
| Back to top |
|
 |
| maxis |
| Posted: Tue Oct 22, 2002 8:26 am Post subject: |
|
|
Centurion
Joined: 25 Jun 2002
Posts: 144
|
I've not heard of session Time out in MQSession. One crude way to test would be, check how long to connections holds - ie. check input count or output count at random interval of time. This may not be effective solution for this .... but atleast till u optimize  your code, you can try this one
If u find about Session timing pl share in the board ..
M |
|
| Back to top |
|
|
| kingdon |
| Posted: Tue Oct 22, 2002 10:37 pm Post subject: |
|
|
Acolyte
Joined: 14 Jan 2002
Posts: 63
Location: UK
|
It's not a session timeout. The most likely cause is wrapping circular logs during the long transaction.
Cheers,
James. |
|
| 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
|
|
|
|
