| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ Explorer browse depth greater than current queue depth |
View previous topic :: View next topic |
| Author |
Message
|
| rickwatsonb |
 Posted: Thu Jan 08, 2015 1:21 pm Post subject: MQ Explorer browse depth greater than current queue depth |
 |
|
Voyager
Joined: 15 Aug 2006
Posts: 87
Location: USA: Mid-West
|
Hi,
Why would a browse in MQ Explorer bring back thousands more messages that what the “current queue depth” states in MQ Explorer?
The MQ Explorer “current queue depth” stays in the range of 250-280 (hitting the refresh button), but a browse in MQ Explorer always brings back 5000 (since I set it to the max of 5000).
The 5000 messages that were browsed have time stamps in the range of 30 to 25 seconds between the youngest and oldest, and the time stamps for all of the messages in each “browse” are always new (examples shown below).
| Code: |
MQ Explorer “current queue depth” = 268 but 5000 messages browsed
Jan 8, 2015 3:32:07 PM – Youngest message
Jan 8, 2015 3:32:37 PM – Oldest message (30 seconds elapsed time)
REFRESH…
MQ Explorer “current queue depth” = 267 but 5000 messages browsed
Jan 8, 2015 3:56:01 PM- Youngest message
Jan 8, 2015 3:56:25 PM – Oldest message (24 seconds elapsed time) |
I copied the queue file to a temp folder and can see that there are NOT 5000 (XML) messages.
Why is the MQ Explorer browse displaying thousands more messages than the “current queue depth” in MQ Explorer (and via MQSC - display q)? What is causing this to be out of sync?
Is this because the messages are being queued and dequeued extremely fast? If so, why is the "current queue depth" inaccurate?
Thanks for your help. |
|
| Back to top |
|
 |
| PaulClarke |
| Posted: Thu Jan 08, 2015 1:30 pm Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
Are you browsing an active queue then? This can yield strange results. If the browser is fairly slow in traversing the list of queues then it is possible that new messages arriving on the queue are seen before the browser gets the 2033 reason code. Meanwhile, presumably, the first few messages it returns have already been processed and are no longer on the queue.
This is always an issue, to some extent, when you are trying to take a snap-shot of a moving target. Do you get same effect when you browse the queue using my SupportPacs MA01, MO03 or MO71 ?
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| 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
|
|
|
|
