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 » Stranded Uncommitted messages and dspmqtrn

Post new topic  Reply to topic
 Stranded Uncommitted messages and dspmqtrn « View previous topic :: View next topic » 
Author Message
PeterPotkay
PostPosted: Tue May 22, 2007 10:33 am    Post subject: Stranded Uncommitted messages and dspmqtrn Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

I had a transmit queue with 19 messages stuck on it. The channel was working fine sending hundreds of messages all along. A Queue Status on the XMITQ showed that there were 19 uncommitted messages on it. The only process that had the XMITQ open was the channel. Looks like the app put the messages under syncpoint, closed the remote q def, but never committed. It was like this for 2 days. The channel was not In Doubt.

I stopped the channel so IPROCS and OPROCS went to zero. But the 19 uncommitted messages remained.

I ran dspmqtrn and got about 12 entries like this:
Code:

E:\>dspmqtrn -m MyQueueManager -e
AMQ7056: Transaction number 0,74445.

    XID: formatID 4478019, gtrid_length 16, bqual_length 48
         gtrid [FFFF07FF606D6749FF1EFFFFFFFF6858]
         bqual [063DFFFFFF257B4EFFFFFFFFFFFF7F52FFFFFF0FFFFF2848FFFF79FFFFFF5AFF
4CFFFF1DFFFFFF48FF020137097DFFFF]

I then ran the rsvmqtrn command:
Code:

E:\>rsvmqtrn -m MyQueueManager -c 0,74445
The transaction has been committed.


That did nothing, so I ran it one by one for all 12 uncommitted transactions and that finally released the 19 messages. The channel grabbed them and shipped them. This was a test system, so I wasn't to worried about forcing the commits. But if you have multiple queues with some uncommitted messages, and dspmqtrn returns a whole bunch of entries, how do you match up an outstanding uncommitted transaction returned by dspmqtrn with a particular set of uncommitted messages that you are trying to force a commit on? I'm sure some of the 12 uncommitted entries I force committed had nothing to do with the problem of the 19 stuck messages, and I probably interfered with some live transactions. I want to avoid that if I need to do this one day in Production.

MQ 5.3.0.8
Windows 2003 SP1
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Stranded Uncommitted messages and dspmqtrn
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.