|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
How to show number of uncommited messages |
« View previous topic :: View next topic » |
Author |
Message
|
karstenj |
Posted: Fri Aug 23, 2002 4:24 am Post subject: How to show number of uncommited messages |
|
|
 Newbie
Joined: 23 Aug 2002 Posts: 4 Location: Denmark
|
Hi,
is there a way to show the number of uncommitted messages on a queue or queuemanager ?
I have an application that gets messages of a queue but dosn't commit the get. When the application terminates, mq restores the queue.
The application has been fixed, but I would like to be able to detect this later on.
Regards
Karsten |
|
Back to top |
|
 |
Glen Shubert |
Posted: Fri Aug 23, 2002 6:17 am Post subject: |
|
|
 Apprentice
Joined: 16 May 2001 Posts: 42 Location: TSYS - Columbus, GA
|
You can do a DIS QMGR ALL command. Then the MAXUMSGS parameter will show what it is set to. _________________ Glen Shubert
Associate Director
MQSeries Technical Support
TSYS |
|
Back to top |
|
 |
bob_buxton |
Posted: Fri Aug 23, 2002 6:26 am Post subject: |
|
|
 Master
Joined: 23 Aug 2001 Posts: 266 Location: England
|
MaxUncommitedMsgs is the maximum number allowed within a Unit Of Work.
I don't think anything shows how many are currently uncommited since the number could change faster than the data could be collected.
Bob _________________ Bob Buxton
Ex-Websphere MQ Development |
|
Back to top |
|
 |
bduncan |
Posted: Fri Aug 23, 2002 8:52 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001 Posts: 1554 Location: Silicon Valley
|
I believe there is a way, although I think it would only work with local queues. Basically, the 'dis ql(xxx) curdepth' command in runmqsc will show the depth of the queue, both committed and non-committed messages. If your application is doing MQGETs from this queue under syncpoint, you can use system() calls (in C, perl, etc) to execute runmqsc, and obtain the number of messages on the queue. Then you can run a MQINQ command to determine the queue depth (in this case, only committed messages). Compare the two values, and the difference should be the number of messages you have removed with MQGETs but haven't committed yet.
Keep in mind this will only work with local queues, and only those queues for which a single application is getting or putting messages. Obviously multiple applications each with units of work against the queue make this method useless... _________________ Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
Back to top |
|
 |
karstenj |
Posted: Sat Aug 24, 2002 3:41 am Post subject: |
|
|
 Newbie
Joined: 23 Aug 2002 Posts: 4 Location: Denmark
|
the thing is that you can actually get the message of the queue and all other applications will see the curdepth without that message. If an error causes the app that is not committing the queues will be restored. It would be nice for monitoring and debugging purposes to be able to see the amount of pending work.
Maybe it can be found somehow using mqinq ? Do you know of any monitoring tool that can show this ? |
|
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
|
|
|
|