|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
need information about current Depth |
« View previous topic :: View next topic » |
Author |
Message
|
mdeba |
Posted: Wed Mar 02, 2005 7:22 am Post subject: need information about current Depth |
|
|
Newbie
Joined: 02 Mar 2005 Posts: 2
|
Hi All,
This is my first subject to this Forume.
I have a local queue in a queue manager,whose current depth is showing as 4.When I browse the queue,there is only 3 messages are there.
If anyone have any solution ,please revert me back.
waiting for reply.
Thanks,
Deba |
|
Back to top |
|
 |
bower5932 |
Posted: Wed Mar 02, 2005 7:36 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Aug 2001 Posts: 3023 Location: Dallas, TX, USA
|
You probably have an uncommitted message. They count against the current depth of the queue. |
|
Back to top |
|
 |
EddieA |
Posted: Wed Mar 02, 2005 9:49 am Post subject: |
|
|
 Jedi
Joined: 28 Jun 2001 Posts: 2453 Location: Los Angeles
|
Quote: |
When I browse the queue,there is only 3 messages are there |
After the browse, what did the depth show. If it was 4, then Ron's answer is probably the reason. If it was 3, then you had an expired message on the queue.
Cheers, _________________ Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
Back to top |
|
 |
mdeba |
Posted: Thu Mar 03, 2005 12:04 am Post subject: need information about current Depth |
|
|
Newbie
Joined: 02 Mar 2005 Posts: 2
|
Hi Eddie,
It is nice to get a reply from you and bower.
After browsing the queue there is only 3 messages in the queue,but the current depth is 4.
Yesterday after restarting the mq server the extra count message had gone out and the current depth is showing as 3. Today I again faced the same problem as before on the same queue as one more current depth. What is a expired message you mean to say?
please give me the details,so that i can not face the problem in future.
Thanks,
Deba |
|
Back to top |
|
 |
fjb_saper |
Posted: Thu Mar 03, 2005 7:10 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
We have seen this type of problems on an xmitq.
It seems to be caused by the usage of a non J2EE but XA compliant transaction manager (ATG) using JMS.
The message is on the queue but not in a gettable state. Might have been rolled back. The problem here seems to be the non j2ee compliance of the transaction manager and how the transactional boundaries and enrollment/release of the MQ XA resource in the XA transaction is being handled.
The difference to an expired message. New messages will be put on the transmission queue and flow through the channel. The channel agent does a get. However the "ghost message" does not disappear. This happens on an xmitq because we are just posting to remote queues. If we were posting to local queues I have no doubt the behavior would be the same.
On a local queue the next get should remove and expired message but will not remove a "ghost message".
A bouncing of the qmgr made those messages disappear every time.
Enjoy  |
|
Back to top |
|
 |
bower5932 |
Posted: Thu Mar 03, 2005 7:20 am Post subject: Re: need information about current Depth |
|
|
 Jedi Knight
Joined: 27 Aug 2001 Posts: 3023 Location: Dallas, TX, USA
|
mdeba wrote: |
What is a expired message you mean to say? |
When you put messages onto a queue, you can give them a time at which they expire (ie, they can be gotten rid of). WMQ doesn't get rid of these messages as soon as they expire, but only when an attempt is made to actually get one of them. If you have a current depth of 4, issue the browse, get three messages, and the depth is now 3, then you had an expired message that WMQ got rid of.
To be safe, you can specify that you don't ever want your messages to expiry. |
|
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
|
|
|
|