|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
ExpiryInterval - What do you have it set at? (z/OS 5.3 only) |
« View previous topic :: View next topic » |
Author |
Message
|
PeterPotkay |
Posted: Mon Apr 07, 2003 6:56 am Post subject: ExpiryInterval - What do you have it set at? (z/OS 5.3 only) |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
I am wondering if I should bother setting this attribute for my z/OS queue managers and if so, at what value? Does it effect the queue manager and any applications that connect to it if you have the Expiry Clean Up run every 1 minute? What value makes sense to set here?
Set it really low so your queue depths are more "real"? Maybe if I had any Depth triggered queues this would be very important to prevent needless triggering? On the other hand maybe I would want the queue to trigger on a depth of 100 even if 75 of the messages were expired.
Or set it at something like a day, so at the end of the day if you browse a queue that had a lot of messages but the depth drops to zero as soon as you hit browse, you are aware that there was some sort of problem during the day?
Or just leave it off? All my queues are being processed as FIFO so the expired messages are getting cleaned up automatically anyway.
The manuals don't give any recommendations. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
oz1ccg |
Posted: Tue Apr 08, 2003 11:43 am Post subject: |
|
|
 Yatiri
Joined: 10 Feb 2002 Posts: 628 Location: Denmark
|
Peter, you're talking Z/OS 5.3... this tlees me we're talking serious applications, and therefore typicly lots of messsages.
How many are lost ? (staying on the queues)
I'm working on a similar case for one of my clients, and we're planning to do the trick in the night when the systems are on low utilization, and therefore have capacity to do that kind of things.
This new service is not free....
Just my $0.02  _________________ Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Tue Apr 08, 2003 12:01 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
There is no specific app I am looking at. I just want to set this value correctly if it will benifit us. We are upgrading to 5.3 in a couple of weeks.
Last week I saw a DLQ in DEV that had a depth of 973 when I came to work in the morning. No one called to complain, but I figured I would check it out. I browsed the queue and poof, the queue went to zero and I had nothing to go on. All the messages were expired. I started asking questions and found who was testing and finally we guessed that because a TCODE was down at the time the front end guys were testing, all the messages going to the bridge queue were going to the DLQ.
If I had set the ExpiryInterval, those 973 messages would have been cleaned up before I would have ever saw them. Is that a good thing or bad thing? I guess bad, since if I never saw that depth I would have never started poking around, and the front end guys would still be wondering why MQ "lost" their messages the night before. But maybe good, since then I would not have been bothered by these expired messages. If the app insists on setting an Expiry of 30 seconds, so be it, but it makes problem resolution sooooo much more tricky.
Seems to me this attribute would have been much more valuable at the queue level, rather than the QM level.
We dont have any applications that are anywhere near having queues fill up with expired messages. Seems to me you would want that sort of problem to show itself. If thousands of messages are piling up on queues and expiring, there has got to be a problem somewhere. I don't want to mask it by cleaning all those messages up all the time.
Right now I am leaning towards leaving it off. _________________ Peter Potkay
Keep Calm and MQ On |
|
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
|
|
|
|