ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » Expired Messages and CURDEPTH

Post new topic  Reply to topic
 Expired Messages and CURDEPTH « View previous topic :: View next topic » 
Author Message
gunter
PostPosted: Thu Oct 13, 2005 6:23 am    Post subject: Expired Messages and CURDEPTH Reply with quote

Partisan

Joined: 21 Jan 2004
Posts: 307
Location: Germany, Frankfurt

Hi,

I'm faced with a, at least for me, strange behavior on MQ 5.3 CSD07 on AIX 5.3.
As I know, and I verified it in the manuals, expired messages stay in the queue until a prozess tries a MQGET for this message. A MQGET with correlation-Id doesn't affect other messages than requestet.

I tried it an the behavior was different.

1. MQPUT with Expire 60 sek, without Correlation-Id
CURDEPTH is 1
2. MQGET with correlation-Id ( timeout 30 sec )
CURDEPTH is still 1
3. MQGET with correlation-Id after 80 seconds
CURDEPTH is still 1
4. MQGET with correlation-Id after four minutes
CURDEPTH is now 0

I'm working on a problem with (mqrc 2033) and like to know whether the messages never arrived or the messages expired.
Until this test I said, the messages never arrived, but now it looks as I have to change my mind.

Missed I something in the documents ?

Thanks.

Gunter
_________________
Gunter Jeschawitz
IBM Certified System Administrator - Websphere MQ, 5.3
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu Oct 13, 2005 6:29 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

It's apparently not guaranteed that expired messages won't get cleaned up behind the scenes.

The only guarantee is that you can't get an expired message.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
wschutz
PostPosted: Thu Oct 13, 2005 6:32 am    Post subject: Reply with quote

Jedi Knight

Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)

and you can always ask for a report message to be sent if a message expires
_________________
-wayne
Back to top
View user's profile Send private message Send e-mail AIM Address
hopsala
PostPosted: Thu Oct 13, 2005 7:00 am    Post subject: Reply with quote

Guardian

Joined: 24 Sep 2004
Posts: 960

We had a discussion about this a while back (Expired messages cleaning), and it was stated that if a queue is "loaded" (meaning it is opened or was opened recently) then some cleaning mechanism does work in the background; sadly, this is undocumented in 5.3 or 6 or anywhere, and remains out of our control completely.
Although it was stated then that this is strictly v6 behavior, your experiment denotes that this may apply to 5.3 CSD07 as well. A better desinged experiment would be beneficial here... (in other words "let someone else do it, i'm on vacation" )
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Expired Messages and CURDEPTH
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.