| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| How do you map the output of dspmqtrn to a specific queue? |
« View previous topic :: View next topic » |
| Author |
Message
|
| PeterPotkay |
 Posted: Tue Feb 16, 2016 1:03 pm Post subject: How do you map the output of dspmqtrn to a specific queue? |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
MQ Server is version 7.5.0.5, RHEL x86-64
MQ Client is version ????, running JMS on Weblogic.
I have 2 local queues used by the same application, each with Uncommitted messages.
The same MQ Client Channel is used for both queues by this one app. The app is running on 2 separate servers.
When a do a Queue Usage Type Queue, I see the UNCOM parameter equal to 5000 on both of these queues
When I do a dspmqtrn –a, I get the below output.
The queues do not have an open Input or Output count.
One of the queues shows a depth of zero, with UNCOM= 5000. I assume that is an unresolved MQGET.
One of the queues shows a depth of 5000, with UNCOM= 5000, can’t browse any of them. I assume that is an unresolved MQPUT.
How do I know which transaction one is for which queue when it comes time to use rsvmtrn?
| Code: |
TranNum(0,11111111)
TRANSTATE(ACTIVE)
UOWLOGDA( ) UOWLOGTI( )
UOWSTDA(2016-02-16) UOWSTTI(10.30.12)
UOWLOG( )
EXTURID(XA_FORMATID[] XA_GTRID[] XA_BQUAL[])
CONN(AA12FD5501C59B2F)
PID(2626) TID(806194)
APPLTAG(Websphere MQ Client for Java)
APPLDESC(WebSphere MQ Channel)
CHANNEL(CHANNEL.A)
CONNAME(xxx.xxx.xxx.xxx)
QMURID(0.15936584)
USERID(ValueofMCAUSER_FromClientChannelHere)
TranNum(0,22222222)
TRANSTATE(ACTIVE)
UOWLOGDA(2016-02-14) UOWLOGTI(20.21.34)
UOWSTDA(2016-02-14) UOWSTTI(20.21.31)
UOWLOG( )
EXTURID(XA_FORMATID[] XA_GTRID[] XA_BQUAL[])
CONN(AA12FD5501C69B2F)
PID(2626) TID(806195)
APPLTAG(Websphere MQ Client for Java)
APPLDESC(WebSphere MQ Channel)
CHANNEL(CHANNEL.A)
CONNAME(yyy.yyy.yyy.yyyy)
QMURID(0.15528698)
USERID(ValueofMCAUSER_FromClientChannelHere) |
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Feb 16, 2016 1:41 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
May be you can differentiate by date and time of the UOW?
Would not know how to follow up with the QMURID but I would expect that to be an id assigned by the transaction manager to the resource manager...
And then again, trying to differentiate by queue may be meaningless. Think about a transaction reading from queue A and putting to queue B...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Feb 16, 2016 3:20 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Adding the -q flag to the dspmqtrn command provided the q names. I thought -a meant ALL and would show everything. Nope, -a plus -q shows more.
To your point FJ, indeed some of the transactions show 2 queues.
Andy H also gave the reminder that rsvmqtrn will not work against transactions that are active, as my examples are. In this case you says I could use the STOP CONN command to force a roll back. Wonder if a force stop of the MQ Client channel would accomplish the same thing.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Feb 16, 2016 4:53 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| PeterPotkay wrote: |
Adding the -q flag to the dspmqtrn command provided the q names. I thought -a meant ALL and would show everything. Nope, -a plus -q shows more.
To your point FJ, indeed some of the transactions show 2 queues.
Andy H also gave the reminder that rsvmqtrn will not work against transactions that are active, as my examples are. In this case you says I could use the STOP CONN command to force a roll back. Wonder if a force stop of the MQ Client channel would accomplish the same thing. |
Sometimes it does. Sometimes it makes the transaction become a ghost....
MQ as resource manager expecting it to be picked up by the transaction manager when said transaction manager (WAS?) has written it off. Only way is to bounce the qmgr for those...
What survives the bounce, you should be able to resolve.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Feb 16, 2016 6:12 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| fjb_saper wrote: |
MQ as resource manager expecting it to be picked up by the transaction manager when said transaction manager (WAS?) has written it off. Only way is to bounce the qmgr for those...
What survives the bounce, you should be able to resolve. |
I wonder if we STOP CONN those, it will get them to the point where rsvmqtrn will then work, meaning I can avoid a QM restart.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Feb 17, 2016 5:20 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| PeterPotkay wrote: |
| fjb_saper wrote: |
MQ as resource manager expecting it to be picked up by the transaction manager when said transaction manager (WAS?) has written it off. Only way is to bounce the qmgr for those...
What survives the bounce, you should be able to resolve. |
I wonder if we STOP CONN those, it will get them to the point where rsvmqtrn will then work, meaning I can avoid a QM restart. |
In the past my experience has been that as long as the prepare commit/rollback has not been executed, you either got lucky killing the connection, or you had to bounce the qmgr...
_________________
MQ & Broker admin |
|
| 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
|
|
|
|
