Posted: Sun May 11, 2008 6:31 pm Post subject: AMQ8722: Dead-letter queue handler unable to put message
Newbie
Joined: 04 Mar 2008 Posts: 6
Hi
We have encountered a problem in our Production MQ server. It shows error as "AMQ8722: Dead-letter queue handler unable to put message: Rule 2 Reason 2085"
After that the Qmanager went to Preemptive state. And later we restarted the QManager and now its running fine. Can anybody helps me to find out the root cause.
Posted: Sun May 11, 2008 7:40 pm Post subject: Re: AMQ8722: Dead-letter queue handler unable to put message
Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
preet1 wrote:
We have encountered a problem in our Production MQ server. It shows error as "AMQ8722: Dead-letter queue handler unable to put message: Rule 2 Reason 2085"
where 2085 means MQRC_UNKNOWN_OBJECT_NAME, thats the reason DLQ failed here...
What queue is there in the RULE?
preet1 wrote:
After that the Qmanager went to Preemptive state. And later we restarted the QManager and now its running fine. Can anybody helps me to find out the root cause.
As this happened on a Production Stystem. so you should investigate it throughly....
Please verify the RULE of DLQ handler to find out which queue it is trying to put the message and why it failed to do so.
1 whats there in the logs / Any FDC etc?
Regards
Gayathri _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die
Posted: Mon May 12, 2008 12:51 am Post subject: Re: AMQ8722: Dead-letter queue handler unable to put message
Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
preet1 wrote:
It shows error as "AMQ8722: Dead-letter queue handler unable to put message: Rule 2 Reason 2085"
What's "it" in this context? The obvious problem is the dead letter handler is trying to put to a queue that doesn't exist (possibly a dynamic queue that's gone out of scope). Your DLH rules should be written to prevent this kind of circular logic.
preet1 wrote:
After that the Qmanager went to Preemptive state. And later we restarted the QManager and now its running fine. Can anybody helps me to find out the root cause.
You've got a rule error, non-persistent messages and a fair amount of luck. I'd revisit how you handle messages on the DLQ. _________________ Honesty is the best policy.
Insanity is the best defence.
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