| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| UNCOM Messages |
« View previous topic :: View next topic » |
| Author |
Message
|
| venky.kcl |
 Posted: Sat Sep 24, 2016 1:26 am Post subject: UNCOM Messages |
 |
|
Newbie
Joined: 24 Sep 2016
Posts: 1
|
Hi
i got a problem like one of the app guy is not able to pick the messages.
As i see the queue is holding uncommit messgaes.
so i tried to browse the messages and the backout count is showing some of the messages as 0 and some of them as 1.
Question
Does it mean by the backout Count is one messages are damaged messages and is that messgaes are holding the other messages processing?
AMQ8450: Display queue status details.
QUEUE(A) TYPE(QUEUE)
CURDEPTH(3501) IPPROCS(1458)
LGETDATE( ) LGETTIME( )
LPUTDATE( ) LPUTTIME( )
MEDIALOG( ) MONQ(OFF)
MSGAGE( ) OPPROCS(2)
QTIME( , ) UNCOM(1505)
Sorry due to some security i am not able to mention the queue name |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Sat Sep 24, 2016 5:18 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9396
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
AMQ8450: Display queue status details.
QUEUE(A) TYPE(QUEUE)
CURDEPTH(3501) IPPROCS(1458)
LGETDATE( ) LGETTIME( )
LPUTDATE( ) LPUTTIME( )
MEDIALOG( ) MONQ(OFF)
MSGAGE( ) OPPROCS(2)
QTIME( , ) UNCOM(1505)
|
Backout count is the number of times the first (or only) message in the queue has been MQBACKed out - usually because the consuming because the app could not successfully process the msg.
Current depth is the total number of messages in the queue, including both committed and uncommitted (UNCOM) messages.
MQ does not (yet) allow sysadmins to browse UNCOM messages, which makes it painfully difficult to determine which app created them. So, it's difficult to say whether UNCOM(1505) means all 1501 messages are in the same single Unit of Work (syncpoint), or each message is in its own UofW.
Using your qstatus display, there are (were) IPPROCS(1458) that had the queue open for input; and OPPROCS(2) had the queue open for output. What is the security issue that prevents you from further problem-determination? Find someone who is not so constrained.
Most likely, client-bindings apps are at 'fault' for failing to MQCMIT or MQBACK these UNCOM messages. You might DISPLAY QSTATUS to determine which HANDLES have the queue open, by which apps, and by which userids.
Which version/release/mod level of MQ? Of MQ client?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Last edited by bruce2359 on Sat Sep 24, 2016 5:23 am; edited 2 times in total |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Sat Sep 24, 2016 5:18 am Post subject: |
|
|
Jedi
Joined: 25 Mar 2003
Posts: 2494
Location: Melbourne, Australia
|
The 1501 uncommitted msgs are currently held by one or more processes. They will only become visible to other processes when a commit or backout is made on their Unit Of Work.
You will be able to see the other 1996 msgs on the queue. Of these, you can see backout count of 0 of 1. This does not mean that the queue is damaged. It does not mean that the backed out messages are damaged.
_________________
Glenn |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sat Sep 24, 2016 5:26 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9396
Location: US: west coast, almost. Otherwise, enroute.
|
Backed-out doesn't mean that the queue or message is "damaged." Rather, it means only that a consuming app (or environment setting) MQBACKed out the message due to incomplete processing.
Tell us about your application. Is it JMS? WAS? Message Broker?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Andyh |
| Posted: Mon Sep 26, 2016 12:15 am Post subject: |
|
|
Master
Joined: 29 Jul 2010
Posts: 237
|
"MQ does not (yet) allow sysadmins to browse UNCOM messages, which makes it painfully difficult to determine which app created them".
While MQ doesn't allow MQI access to the uncommitted messages, it does provide the dspmqtrn command, which when used with the -q and -a options will show which transactions have updated which objects, and also shows the
ConnId curently associated with those transactions.
You can then use the runmqsc "DIS CONN" command to display further details about the connections associated with those transactions. |
|
| 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
|
|
|
|
