[AMQ-3236] In the case of DLQ processing due to an exception from onMessage, provide the exception string as a message property

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.4.2
• Fix Version/s: 5.5.0, 5.9.0
• Component/s: Broker
• Labels: DLQ Exception Redelivery
• Assignee: Gary Tully
• Reporter: Gary Tully
• Created: 22/Mar/11 13:34
• Updated: 31/Jul/13 11:52
• Resolved: 31/Jul/13 11:51

Description

When an application throws an exception from on message, redelivery kicks in through session rollback. If the policy dictates that the message should be sent to the DLQ, the exception cause is lost.
The enhancement would pipe the exception with the internal poison ack such that it can be included as a message property in the message in the DLQ.

Some context in the answer http://stackoverflow.com/questions/5069733/preservation-of-exception-cause-when-redelivering-failed-activemq-jms-messages-pr/5109361#5109361

Issue Links

• is related to: AMQ-2021 durable subscriber gets stuck while using persistent delivery mode and client acknowledgment with session.recover().