Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Tue, 8 Sep 2015 09:11:46 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12741294.1410661691000.277173.1441703506416@Atlassian.JIRA>
In-Reply-To: <JIRA.12741294.1410661691000@Atlassian.JIRA>
References: <JIRA.12741294.1410661691000@Atlassian.JIRA>
 <JIRA.12741294.1410661691763@arcas>
Subject: [jira] [Resolved] (CAMEL-7813) Make camel-jms more robust for
 replyTo
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Claus Ibsen resolved CAMEL-7813.
--------------------------------
    Resolution: Fixed

> 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
>            Assignee: Claus Ibsen
>            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)