| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Dead Letter Queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| LH33 |
 Posted: Mon Jan 26, 2004 11:22 am Post subject: Dead Letter Queue |
 |
|
Master
Joined: 21 Nov 2002
Posts: 200
|
I have a message flow that has been running fine for several months. Recently, I have noticed that Intermittently, a message is written to the Dead Letter Queue. What would cause a message to be written to the Dead Letter Queue?
By the way - I took the message off the Dead Letter Queue and put it back on the input queue a few seconds later and it worked fine.
Thanks!! Lisa |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Jan 26, 2004 11:37 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The main reason it would go to the Dead Letter Queue is if you do not have a backout queue configured on the input queue, and an error occurred that caused the message to propogate to the failure terminal of the Input node.
Other reasons would include the normal reasons that MQ messages go to the DLQ.
What was the Reason Code on the Dead Letter Header? That will help you figure out why it went there (sometimes).
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| LH33 |
| Posted: Mon Jan 26, 2004 12:26 pm Post subject: |
|
|
Master
Joined: 21 Nov 2002
Posts: 200
|
The Reason code indicated that there was an internal software error in the Mesage Broker itself. We have contacted IBM.
Thanks, Lisa |
|
| Back to top |
|
|
| EgilsJ.Rubenis |
| Posted: Tue Jan 27, 2004 1:55 am Post subject: |
|
|
Acolyte
Joined: 18 Nov 2002
Posts: 63
Location: Germany, Alfeld
|
in our environment (z/OS, OS390, SunSolaris) we are working with Cics Transactions. If a CicsTxn fails due to a controlled rollback or a crash the meassage is written to the dlq. also if problems aoccur with the cics bridge.
regards egils |
|
| Back to top |
|
|
| mverh |
| Posted: Tue Jan 27, 2004 12:19 pm Post subject: |
|
|
Voyager
Joined: 06 Mar 2002
Posts: 97
|
If a message flow has no backout queue assigned and you are consuming messages under syncpoint then if the flow abends or an exception is thrown and you do not wire the mqinput node catch terminal then the message will end up on the dlq. The reason code is normally 65536 which is simply generic reason code set by wmqi. Depending on the platform a corresponding entry will logged to the event viewer (W2K), /var/adm/user.log (AIX) etc, also look in the errors directory. This should help you out in figuring out why the message ended up on the dlq.
Note sometimes an EG (Dataflowengine) will abend, bipservice will recognize this and automatically recover by restarting the EG. If the abend was due to something other than the message itself then replaying the message may result in it being processed successfully.
HTH
_________________
Marc Verhiel
IBM Canada Ltd. |
|
| 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
|
|
|
|
