Dealing with poison messages in the dead letter queue

[adap proster]

So how can I differentiate the messages in DLQ. because if I reprocess a poison message from DLQ it would again come back to DLQ.

[Henry Wong]

BTW... this topic was split off from here ... https://coderanch.com/t/316811/java/JMS-rollback-Dead-Letter

Henry

[Henry Wong]

First of all, this is implementation specific, so, it may help us a bit if you mention which messaging environment you are using.... but ... to answer in a general way...

You really shouldn't be processing messages in the dead letter queue. They are there for a reason, and that is, to be examined to figure out what went wrong. If reprocessing was an option, then you could have achieve the same thing by allowing more redeliveries to consumers.

However, if you really want to process messages in the dead letter queue, then one possible option is to have a different policy for the dead letter queue. Having the policy of the same dead letter queue for the dead letter queue is silly. Perhaps, messages from the dead letter queue, that fail delivery, should be discarded? Or perhaps, it should go to a different queue, as its dead letter queue?

Henry