camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-8522) Set OriginalDestination AMQ message property before sending it to DLQ
Date Wed, 06 May 2015 13:11:00 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-8522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14530505#comment-14530505
] 

Claus Ibsen commented on CAMEL-8522:
------------------------------------

There is an unit test with example how this can be done
org.apache.camel.component.jms.ActiveMQOriginalDestinationTest

But to have it out of the box would require ActiveMQ 5.12 with Camel 2.16 onwards are in use.

> 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
>
>
> 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)

Mime
View raw message