| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| DLQ disappearing messages |
« View previous topic :: View next topic » |
| Author |
Message
|
| tczielke |
 Posted: Mon Oct 06, 2014 12:46 pm Post subject: DLQ disappearing messages |
 |
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
I have run into a situation intermittently where I will get to work on Monday morning and find > 1,000 messages on a DLQ. When I go to browse them with different monitoring tools, I get back no messages available and the curdepth of the DLQ is zero. I am thinking what is happening is the messages that got put the DLQ had an expiry that has now passed. I did a quick test of this on my Sandbox, and can seem to recreate this scenario. In other words, the messages that have passed the expiry stay on the queue (i.e. DLQ) until an app actually tries to GET them.
However, I would like to see the contents of these DLQ messages to make sure they are what I think they are. However, if I do a GET to view them, MQ obviously deletes them since they have expired. Any ideas how I could see what the contents of the messages were? I tried running tracing while running an amqsbcg program, to see if I could see the messages in a trace. I traced both the amqsbcg program and the queue manager agent (amqzlaa0). No success.
Without adding some API exit or auditing to capture the message before they get PUT to the DLQ, any ideas how I could see the contents of these expired messages? |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Mon Oct 06, 2014 12:54 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| You might be able to use one of the products by the forum sponsor Cressida to do this. |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Oct 06, 2014 1:01 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Process them when they arrive on the DLQ and change the expiry to non-expiry.
Easy to do with a message broker. Might be possible to do with the runmqdlq program (or change the source of that to do it).
Or run a cron to backup the DLQ every hour (or whatever) using QLOAD.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| tczielke |
| Posted: Tue Oct 07, 2014 4:21 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
| Thanks to all, for the suggestions! |
|
| 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
|
|
|
|
