| Author |
Message
|
| ammx |
 Posted: Tue Aug 21, 2018 7:21 am Post subject: curdepth getting full after clearing |
 |
|
Acolyte
Joined: 08 Sep 2017
Posts: 50
|
Hi
I cleared a queue with the command clear qlocal(QUEUE_NAME) and everything seemed to be fine, the curdepth of the queue was 0, but after like 13 minutes the queue starts getting full again. What could be triggering this? No more messages were sent to that queue after clearing the messages
Thanks in advance |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Aug 21, 2018 7:28 am Post subject: Re: curdepth getting full after clearing |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ammx wrote: |
| No more messages were sent to that queue after clearing the messages |
So where do the messages say they came from?
Is it an application or a system queue?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Aug 21, 2018 8:40 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
What queue precisely? And, what is maxdepth of the queue?
_________________
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 |
|
|
| ammx |
| Posted: Wed Aug 22, 2018 7:39 am Post subject: |
|
|
Acolyte
Joined: 08 Sep 2017
Posts: 50
|
The messages are from a system queue. The queue curdepth is 409421 and the MAXDEPTH is 80000000. On the error logs the only thing I could find is
AMQ7234: 80000 messages from queue 'xxxx' loaded on queue manager 'XXX'
it showed first 80000 messages, then 90000,.....100000 messages |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Aug 22, 2018 7:43 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| ammx wrote: |
| The messages are from a system queue.. |
WHICH one?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Aug 22, 2018 7:55 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ammx wrote: |
| The messages are from a system queue |
And the putting application in the MQMD is......? 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Wed Aug 22, 2018 4:43 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| ammx wrote: |
The messages are from a system queue. The queue curdepth is 409421 and the MAXDEPTH is 80000000. On the error logs the only thing I could find is
AMQ7234: 80000 messages from queue 'xxxx' loaded on queue manager 'XXX'
it showed first 80000 messages, then 90000,.....100000 messages |
This is normal behaviour by MQ. Nothing had consumed any messages for quite a while, so MQ removed its in-memory index cache for the queue. Then something opened the queue, so MQ proceeded to reload its cache. It produces AMQ7234 every 10,000 messages for your information.
This can indicate a message processing issue, as queues should not build up a very large number of messages and not be consumed. The cache reload process can impact qmgr performance. It can also delay the command processor if there are command requests for the queue.
_________________
Glenn |
|
| Back to top |
|
|
|
|
