| Author |
Message
|
| pm4mq |
 Posted: Fri Jan 08, 2010 4:18 pm Post subject: AMQ9544 Messages not put to destination queue. |
 |
|
Newbie
Joined: 08 Jan 2010
Posts: 6
|
Explanation: During the processing of channel '&3' one or more messages could not be put to the destination queue and attempts were made to put them to a dead-letter queue. The location of the queue is &1, where 1 is the local dead-letter queue and 2 is the remote dead-letter queue.
User Response: Examine the contents of the dead-letter queue. Each message is contained in a structure that describes why the message was put to the queue, and to where it was originally addressed. Also look at previous error messages to see if the attempt to put messages to a dead-letter queue failed. The program identifier (PID) of the processing program was '&4'
I did check the dead letter queue but i couldnt see the messages, any body has the idea why this is coming. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Jan 08, 2010 4:40 pm Post subject: Re: AMQ9544 Messages not put to destination queue. |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| pm4mq wrote: |
| I did check the dead letter queue but i couldnt see the messages, any body has the idea why this is coming. |
What about the xmitq that channel serves?
This error has a number of possible causes. Aside from looking in the DLQ, what else have you tried? What is the channel status? Under what circumstances does this error appear?
There's really not enough information in your post to really make a judgement.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| pm4mq |
| Posted: Fri Jan 08, 2010 5:20 pm Post subject: |
|
|
Newbie
Joined: 08 Jan 2010
Posts: 6
|
Nothing in xmitq and the channel is in running state. I would have found out the reason provided if i know the app and its owner. This is basically coming from PM4Data which a dirmon request sending this data. Its getting generated now and then but i dont see any complaints from the app people saying that they have lost the message. I am not sure why this particular message is getting generated. Any ideas where i can do some research would help me if not the exact answer. I have tried to look into the pm4data logs but i dont see any errors there also.
I am little bit confused why its getting generate now and then. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jan 08, 2010 5:35 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| pm4mq wrote: |
| Its getting generated now and then but i dont see any complaints from the app people saying that they have lost the message. |
Well they wouldn't - PM4Data is a commerical file-over-WMQ product. It would be more interesting to know if any of their files were lost, delayed or corrupt.
| pm4mq wrote: |
| I am not sure why this particular message is getting generated. |
The message is the result of an underliverable message.
| pm4mq wrote: |
| Any ideas where i can do some research would help me if not the exact answer. |
You could start by seeing if there's a dead letter handler dealing with the undelivered message automatically before you can find it in the DLQ.
| pm4mq wrote: |
| I have tried to look into the pm4data logs but i dont see any errors there also. |
There wouldn't be, would there? Not on the sending side. It might be more productive to check the logs on the receiving side.
| pm4mq wrote: |
| I am little bit confused why its getting generate now and then. |
A number of possible suggestions spring to mind, that would cause intermitent problems delivering messages.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| pm4mq |
| Posted: Fri Jan 08, 2010 7:54 pm Post subject: |
|
|
Newbie
Joined: 08 Jan 2010
Posts: 6
|
You could start by seeing if there's a dead letter handler dealing with the undelivered message automatically before you can find it in the DLQ.
How to find that there is deadletter handler running on the recieving side?
Even i have seen the same message on the recieving side which is a windows environment. I could see the same error in event viewer.
Its quite interesting, to know how its happening. You r genious man. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sat Jan 09, 2010 8:02 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Look also at the queue manager object DEADQ attribute. DEADQ( ) identifies the name of the dead-letter queue that this qmgr/MCA will attempt to use for undeliverable messages.
Does the queue named in the DEADQ attribute exist?
Is the length of the 'lost' message greater than the max msg length of the dead-letter queue?
Are the 'lost' messages non-persistent?
Is the dead-letter queue put-enabled?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Vitor |
| Posted: Sat Jan 09, 2010 8:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bruce2359 wrote: |
Look also at the queue manager object DEADQ attribute. DEADQ( ) identifies the name of the dead-letter queue that this qmgr/MCA will attempt to use for undeliverable messages.
Does the queue named in the DEADQ attribute exist?
Is the length of the 'lost' message greater than the max msg length of the dead-letter queue?
Are the 'lost' messages non-persistent?
Is the dead-letter queue put-enabled? |
This is all valid advice, but won't address the question of if a dead letter handler is in use.
Clearly all worth checking though. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Sat Jan 09, 2010 8:31 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| pm4mq wrote: |
| How to find that there is deadletter handler running on the recieving side? |
See if one's running, or has been set to be triggered off the dead letter queue - see if the dead letter queue has TRIGGER(ON) while you're checking all the other things my most worthy associate suggested.
| pm4mq wrote: |
| Even i have seen the same message on the recieving side which is a windows environment. I could see the same error in event viewer. |
Well that's a clue, if both sides are throwing the same error, isn't it?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| pm4mq |
| Posted: Sat Jan 09, 2010 4:52 pm Post subject: |
|
|
Newbie
Joined: 08 Jan 2010
Posts: 6
|
Look also at the queue manager object DEADQ attribute. DEADQ( ) identifies the name of the dead-letter queue that this qmgr/MCA will attempt to use for undeliverable messages.
ANS: Yes the deadq is assigned with SYSTEM.DEAD.LETTER.QUEUE.
Does the queue named in the DEADQ attribute exist?
ANS: Yes it does exist.
Is the length of the 'lost' message greater than the max msg length of the dead-letter queue?
Max msglen of the dead letter queue is 9999999, message is not bigger than this.
Are the 'lost' messages non-persistent?
ANS: They are not lost, not tracable no body complaints about the loss of the message.
Is the dead-letter queue put-enabled?
ANS: Yes its put enabled. |
|
| Back to top |
|
|
| pm4mq |
| Posted: Sat Jan 09, 2010 4:54 pm Post subject: |
|
|
Newbie
Joined: 08 Jan 2010
Posts: 6
|
Victor
| Quote: |
| See if one's running, or has been set to be triggered off the dead letter queue - see if the dead letter queue has TRIGGER(ON) while you're checking all the other things my most worthy associate suggested |
.
ANS: I dont see the trigger is on . I see NOTRIGGER. |
|
| Back to top |
|
|
| pm4mq |
| Posted: Sat Jan 09, 2010 4:59 pm Post subject: |
|
|
Newbie
Joined: 08 Jan 2010
Posts: 6
|
[VictorWell that's a clue, if both sides are throwing the same error, isn't it[/Victor]?
I didnt understand this exactly, can you be clear about this.
By knowing all these info still we are not sure where the message has gone, any new questions or thoughts highly appreciated. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Jan 09, 2010 6:09 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Vitor wrote: |
| pm4mq wrote: |
| How to find that there is deadletter handler running on the receiving side? |
|
Talk to the MQ Admin. If you need to stop a DLQ handler you can temporarily get inhibit the DLQ. This should have the handler exit.
A give away is the number of IPProcs > 0
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
