| Author |
Message
|
| mqlost |
 Posted: Fri Feb 10, 2006 5:09 am Post subject: Removing an uncommitted message from a XmitQ |
 |
|
Newbie
Joined: 10 Feb 2006
Posts: 7
|
I have problems getting rid of an uncommitted message on a XmitQ. I know how to remove uncommitted messages from queue's and have done it a few times but when I use dspmqtrn to get the transaction number of the message I don't get the transaction number from the message in the XmitQ. And without that number I can't use rsvmqtrn.
Does anyone know how to get the message from the queue without having to restart the queuemanager. This is a high availability environment and I would like to keep the down time to a minimum.
edit: Some extra information. The channel responsible for tranporting the message has the status running not indoubt. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Feb 10, 2006 5:18 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
One option that's slightly less nuclear than restarting the QM is to stop the channel, and delete and recreate the XMITQ.
In fact, you might see if stopping the channel allows you to see the tran id for the uncommitted message.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Fri Feb 10, 2006 6:57 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
how about resolving the channel? if the channel is indoubt and you use backout the message should remain on the xmitq (but can be purged), if it is committed it should disappear (this may either be the correct action, or you will doublicate or erase a message, depending whether it has already reached the other end of the channel).
or is it the putting application that is indoubt?
_________________
Regards, Butcher |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Feb 10, 2006 2:15 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
There is a third problem that might occur here:
If the putting application quit and never committed the message used an xa transaction and never did the commit prepare you cannot access the message. There is nothing under dspmqtrn.
Those messages in my experience disappear when you recycle the qmgr.( shutdown -- start). (It's magic) 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqlost |
| Posted: Thu Feb 16, 2006 1:27 am Post subject: |
|
|
Newbie
Joined: 10 Feb 2006
Posts: 7
|
| Thanks to the latest microsoft security patch we had the opportunity to do something. I tried the first suggestion and stopping the channel worked. I was able to get the transaction number and to commit the message. |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Feb 16, 2006 3:18 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| mqlost wrote: |
| Thanks to the latest microsoft security patch we had the opportunity to do something. I tried the first suggestion and stopping the channel worked. I was able to get the transaction number and to commit the message. |
Can you explain how microsoft security patches are related to the problem of uncommitted messages?
_________________
-wayne |
|
| Back to top |
|
|
| mqlost |
| Posted: Thu Feb 16, 2006 5:32 am Post subject: |
|
|
Newbie
Joined: 10 Feb 2006
Posts: 7
|
| It''s very simple. The problem existed a High Availabilty Sun cluster that is connected to a Windows 2003 Server. This server needed the security patch and we had therefor the opportunity to stop the channel to try out the suggested solution. |
|
| Back to top |
|
|
|
|
