| Author |
Message
|
| anveshita |
 Posted: Fri Jun 05, 2009 11:45 am Post subject: dead letter queue message |
 |
|
Master
Joined: 27 Sep 2004
Posts: 254
Location: Jambudweepam
|
| I have a message in dead letter queue and would like to know the channel through which the message came in. I have checked the properties of the message using MQ Explorer to find this out, but could not. Any help? |
|
| Back to top |
|
 |
| ucbus1 |
| Posted: Fri Jun 05, 2009 11:54 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
hmm.
Can you check in the MQ error logs? I think the error message could be AMQ9544 or something similar. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jun 05, 2009 12:06 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
If the message ended up on the DLQ after being sent over a channel, it ended up there because it could not be delivered where it was supposed to be delivered. And everything you need to know about where it was supposed to be delivered would be in the DLQ Header on the message.
If you have unique MCAUSERs on all of your incoming channels, you can tell from that what channel the message came from.
If you do not have unique MCAUSERs on all of your incoming channels, you probably have a security problem. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jun 05, 2009 2:51 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The MQMD of the message probably also has the sender qmgr name on it.
You just need to understand the route the message took.
You can also have the sending party use the messaging traceroute utility (V6)
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Fri Jun 05, 2009 7:12 pm Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
|
| Back to top |
|
|
| exerk |
| Posted: Sat Jun 06, 2009 2:10 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| fjb_saper wrote: |
| ...You just need to understand the route the message took... |
You should have documented 'message maps', which show the originating object, and every intermediate object 'through' which it travels.
| fjb_saper wrote: |
| ...You can also have the sending party use the messaging traceroute utility (V6)... |
Of great assistance in cases where you are back-filling information.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| anveshita |
| Posted: Wed Jun 10, 2009 6:27 am Post subject: |
|
|
Master
Joined: 27 Sep 2004
Posts: 254
Location: Jambudweepam
|
Thanks all.
I could find the channel name on which we are receiving the messages.
Now I tried to see the message using mq exlporer on the DLQ, but it shows the message partly. If I want to access the whole messages how can I do browse the whole message insted of part as shown in MQ Explorer. |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Jun 10, 2009 6:32 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| anveshita wrote: |
| ...If I want to access the whole messages how can I do browse the whole message insted of part as shown in MQ Explorer... |
Why would you want to? But MO71 will do the job, amongst other things.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Jun 10, 2009 6:54 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| RFHUTIL/RFHUTILC may be better for this as it can display the DLH and prepare messages for re-sending. |
|
| Back to top |
|
|
| anveshita |
| Posted: Wed Jun 10, 2009 7:09 am Post subject: |
|
|
Master
Joined: 27 Sep 2004
Posts: 254
Location: Jambudweepam
|
| I would like to know the message content to debug further. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jun 10, 2009 7:16 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| anveshita wrote: |
| I would like to know the message content to debug further. |
It's unusual for a message to be dead lettered on content grounds. Unless you're going against best practice and using the DLQ for application errors.
But either of the support pacs named will do this for you just fine.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Wed Jun 10, 2009 8:17 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| Vitor wrote: |
| anveshita wrote: |
| I would like to know the message content to debug further. |
It's unusual for a message to be dead lettered on content grounds. Unless you're going against best practice and using the DLQ for application errors.
But either of the support pacs named will do this for you just fine. |
As the best practice, don't keep the messages on the DLQ. You can take action as Discard, Ignore, Forward or Retry.
I think , in your case 'Forward' will be better solution. But to check the channel name you must know from where its coming and whats the destination. As its already said in the above posts.
Another thing...
To see the content browse queue command can be used to display the content ; amqsbcg.
Lots of other tool are there in the market to view the contents of a message in a queue , as MQJExplorer.
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
|
|
