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

["Gary Tully (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-3236.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 5.9.0

fix in http://svn.apache.org/r1508819
new props applied to a message copy
                
> In the case of DLQ processing due to an exception from onMessage, provide the exception string as a message property 
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-3236
>                 URL: https://issues.apache.org/jira/browse/AMQ-3236
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker
>    Affects Versions: 5.4.2
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>              Labels: DLQ, Exception, Redelivery
>             Fix For: 5.9.0, 5.5.0
>
>
> 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

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira