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] [Updated] (CAMEL-7813) Make camel-jms more robust for replyTo
Date Sat, 21 Mar 2015 10:03:38 GMT

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

Claus Ibsen updated CAMEL-7813:
-------------------------------
    Fix Version/s: 2.16.0

> Make camel-jms more robust for replyTo
> --------------------------------------
>
>                 Key: CAMEL-7813
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7813
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jms
>    Affects Versions: 2.13.2
>            Reporter: Edward Ost
>            Priority: Minor
>             Fix For: 2.16.0
>
>
> When a JMS queue is used as a camel consumer for a route it may well be one of possibly
many intermediate stops in a chain of processing.  If the previous processing step itself
used Camel to route the message, then both the JMS replyTo and the camel-header JMSReplyTo
will both be populated with the same value.  This will cause an infinite loop.
> Of course, this is in some sense a developer error, but it is a pain to constantly add
code to clear the camel JMSReplyTo header if it equals the destination.  This should probably
be internal to the camel-jms component itself.



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

Mime
View raw message