[
https://issues.apache.org/jira/browse/CAMEL-8522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15155517#comment-15155517
]
Claus Ibsen commented on CAMEL-8522:
------------------------------------
The implementation will be out of the box in ActiveMQ 5.14 onwards. For using
ActiveMQ 5.13 or older, there is a custom strategy you can use yourself in the
unit test: org.apache.camel.component.jms.ActiveMQOriginalDestinationTest
> 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.17.0
>
>
> 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)
