ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » Removing uncommitted messages from a Queue.

Post new topic  Reply to topic Goto page Previous  1, 2
 Removing uncommitted messages from a Queue. « View previous topic :: View next topic » 
Author Message
T4ss1nf
PostPosted: Mon May 18, 2009 3:23 am    Post subject: Reply with quote

Newbie

Joined: 30 Sep 2008
Posts: 6



Thanks to fjb_saper for pointing to dspmqtrn (Display In-Doubt Transactions).

Code:
dspmqtrn -m[ourQueueManager]


With this utility we have found a number of in-doubt transactions that remains for days. All these transactions were externally coordinated.
With the help of the XIDs we found the in doubt transaction that was responsible of the remaining message on our queue.

We used the following command to backout the in-doubt transaction.

Code:
rsvmqtrn -m[ourQueueManager] -b [Transaction],[Number]


Note: [Transaction],[Number] can be found in the output of dspmqtrn.

Then comes the magic : The uncommitted message disappeared, the queue status is back to normal.

With the information present in this post we can now retrace what has conduct to this situation.

- The sending application put a message on the queue. Everything went good.
- The receiving application within a transaction did a call to MQGET which decrease the QDepth. But before definitely removing the message from the Queue the QueueManager waited for the final transaction manager commit.
- But for some reason the transaction never commit and the transaction manager was never able to even send a commit or backout message to our QueueManager.
- During days the QueueManager waited patiently for the Transaction Manager to inform it about the results of the in-doubt transaction without success.
- We manually ended its long wait.

I will now investigate what happened to the external transaction manager. And what are all these other in-doubt transactions still present.

Thanks everyone for your precious help.

One last question, by any chance, does anyone has a clue about an in-doubt transaction timeout (before back-out) or something else that could help us manage these never-ending transactions?

In the meantime, we are running a self made script that will report these long-running in-doubt transactions.

F.
Back to top
View user's profile Send private message
zpat
PostPosted: Mon May 18, 2009 3:27 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

That's what I said in the second post here - why does no-one ever believe a concise answer?
Back to top
View user's profile Send private message
kevinf2349
PostPosted: Mon May 18, 2009 4:52 am    Post subject: Reply with quote

Grand Master

Joined: 28 Feb 2003
Posts: 1311
Location: USA

zpat wrote:
That's what I said in the second post here - why does no-one ever believe a concise answer?


Because, for some reason, nobody ever believes their application programmers write crappy code. They always take the programmers 'my code is good' word for it. Why? Probably because the code does what they want it to even if it blows the infrastructure up from time to time. That is obviously an infrstructure issue right?
Back to top
View user's profile Send private message
T4ss1nf
PostPosted: Mon May 18, 2009 5:21 am    Post subject: Reply with quote

Newbie

Joined: 30 Sep 2008
Posts: 6

zpat wrote:
That's what I said in the second post here - why does no-one ever believe a concise answer?


Because you didn't read my concise question . In my first post I was telling that the getting application was stopped multiple time since the uncommitted message was there. Unfortunately, your reply asking me to stop the receiving application to force the commit didn't convince me.

About concise answer, read my last reply, I mostly thank fjb_saper who has the most concise (one-line) answer.

Thanks anyway,
F
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon May 18, 2009 8:28 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

Here is the 3 liner:
It may be a getting application
It may be a putting application
In any case the TM issued a prepare commit on the XA transaction and never committed...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » General IBM MQ Support » Removing uncommitted messages from a Queue.
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.