You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2015/05/04 16:27:06 UTC

[jira] [Updated] (CAMEL-8522) Set OriginalDestination AMQ message property before sending it to DLQ

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

Willem Jiang updated CAMEL-8522:
--------------------------------
    Fix Version/s:     (was: 2.15.2)
                   2.15.3

> Set OriginalDestination AMQ message property before sending it to DLQ
> ---------------------------------------------------------------------
>
>                 Key: CAMEL-8522
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8522
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-activemq
>            Reporter: Susan Javurek
>            Assignee: Claus Ibsen
>             Fix For: 2.16.0, 2.15.3
>
>
> Can we consider setting OriginalDestination property on the ActiveMQMessage when sending it to the DLQ in Camel?
> That would be useful for tools like Hawt.io or FMC. For example FMC relies on the OriginalDestination to provide "retry" functionality. Currently Camel doesn't set OriginalDestination, so we can't retry the delivery of the AMQ messages from Camel DLQ.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)