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 Sun, 05 Apr 2015 16:36:33 GMT

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

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

This may require a change in activemq-camel in Apache AMQ instead where we can have additional
logic when creating the JMS message to send to the DLQ. Then it could detect that the original
message is a JMS message from AMQ and grab the original destination if exists.

Otherwise we would need to rely on reflection which we dont want the overhead off using.

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