| Author |
Message
|
| WBI_user |
 Posted: Mon Aug 25, 2008 5:26 am Post subject: Curdepth mystery |
 |
|
Partisan
Joined: 07 Aug 2001
Posts: 386
|
We are running MQ Version: 6.0.2.1 on AIX.
An application support has complained to us that they are losing some messages. The MQ program is from 3rd party with no source code.
The observation is as follow:
The application runs at night and puts 34668 messages on a queue. But we only found 15631 messages in the morning. The only explanation we have for them is the message expired. But the vendor claimed that they do no put expiry time on the message.
We worked with the application support last night and check the queue form time to time using MQ Explorer. The entire application runs about 5 minutes. At curdepth 26129, the queue showed no application open for Input, no uncommitted messages. We then did a refresh and noticed the curdepth dropped to 18381. We then lat it runs to completion. The final queue depth was 15631.
I cannot think of any explanation other then message expiry. But I need to show some evidence.
Is there any queue statistics from standard WMQ V6 showing number of messages expired?
Any other suggestion or explanation for this? They said that they have message grouping in their application logic. Can this be related? |
|
| Back to top |
|
 |
| kevinf2349 |
| Posted: Mon Aug 25, 2008 6:43 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
We had a similar 'hit' when a thrid party vendor was using MQ to file transfer. They were hitting the max queue depth and so the queue was showing uncommitted messages in the depth until the transfer failed and rolled back.
We 'fixed' it by increasing the maxdepth of the queue. |
|
| Back to top |
|
|
| WBI_user |
| Posted: Mon Aug 25, 2008 6:54 am Post subject: |
|
|
Partisan
Joined: 07 Aug 2001
Posts: 386
|
| In our case, there is still lots of room in queue depth and queue status shows no uncommitted messages. |
|
| Back to top |
|
|
| jeevan |
| Posted: Mon Aug 25, 2008 8:58 am Post subject: Re: Curdepth mystery |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| WBI_user wrote: |
We are running MQ Version: 6.0.2.1 on AIX.
An application support has complained to us that they are losing some messages. The MQ program is from 3rd party with no source code.
The observation is as follow:
The application runs at night and puts 34668 messages on a queue. But we only found 15631 messages in the morning. The only explanation we have for them is the message expired. But the vendor claimed that they do no put expiry time on the message.
We worked with the application support last night and check the queue form time to time using MQ Explorer. The entire application runs about 5 minutes. At curdepth 26129, the queue showed no application open for Input, no uncommitted messages. We then did a refresh and noticed the curdepth dropped to 18381. We then lat it runs to completion. The final queue depth was 15631.
I cannot think of any explanation other then message expiry. But I need to show some evidence.
Is there any queue statistics from standard WMQ V6 showing number of messages expired?
Any other suggestion or explanation for this? They said that they have message grouping in their application logic. Can this be related? |
You can use the queue stat sample java program to get enqueue and dequeue. is the two do not match, ( in fact including the current depth),
eg enqueue <> dequeue+curdepth, then message might have been expired. |
|
| Back to top |
|
|
| SAFraser |
| Posted: Mon Aug 25, 2008 10:53 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
| Nothing in the queue manager log? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Aug 25, 2008 10:58 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
May be it is an application that is not keeping the queue open but reads the messages and as such does not show in ipprocs...
You could get inhibit the destination queue and providing there is a large enough log you should be fine.
Check the log for message rolled back on long running transaction..... (your log might not be large enough
Check the sender app's JNDI definition of the target queue to verify there is no expiry set.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| SAFraser |
| Posted: Mon Aug 25, 2008 12:23 pm Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
| Yes, I was thinking along the lines of circular logs being short of space, and possible rollbacks. |
|
| Back to top |
|
|
|
|
