Posted: Wed Oct 01, 2008 1:02 am Post subject: Websphere MQ Not Empty - UnCommitted transactions in MQ
Newbie
Joined: 30 Sep 2008 Posts: 8
Hi all,
I am facing some severe issues with MQ which is creating show stopper issues. I am using MQ for putting and getting messages which is in a Transaction Scope enlisted with JOTM's Transaction Manager along with an Oracle Database XA Resource. When the process is started messages are flowing in and out correctly.
But when i stop the process inbetween when messages are flowing. Some transactions are left uncommitted in the MQ. When i try to clear the Queue i get the followin error in some of the MQ's.
AMQ:8143:WebSphere MQ Not Empty
I tried to get the transactions which are uncommitted using the dspmqtrn.
I got the transaction numbers with the above command.
I backed out the transactions with the command rsvmqtrn.
Some Queues got resolved with the above process.
But the problem now is, some of the MQ's still remains in "Websphere MQ Not Empty" status when i try to clear the Queue
dspmqtrn is not returning and Uncommitted transaction Numbers. Some messages are there in the Queue. I can see in the CURDEPTH attribute. I even tried writing a sample GET program to get out the messages. But its returning a No Message Exception (2033) even if CURDEPTH is showing some value > 0
yes. its strange. Whenever i stop the process inbetween when transactions are in progress. Its acceptable that some transactions may remain uncommitted when system exit happens. But why does this "Websphere MQ Not Empty" message comes even when dspmqtrn is not returning any uncommitted transactions?
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