You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Minh Tran <da...@gmail.com> on 2015/01/12 04:45:01 UTC

JMSReplyTo not being removed

Hi

It seems that when Camel replies to a message, it does not remove the JMSReplyTo header off the reply. I have looked at the unit test testSendInOnlyWithReplyTo in Camel’s unit tests and there’s a comment there that describes having to ignore this field being sent.

// we should disable reply to to avoid sending the message back to our self
// after we have consumed it

This is not a good solution if the listener happens to be a separate application. They wouldn’t have any idea to ignore the JMSReplyTo header. Wouldn’t this be classified as a bug? Camel should remove this field out when replying shouldn’t it?

Re: JMSReplyTo not being removed

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

Yeah I think we have logged a ticket about this
https://issues.apache.org/jira/browse/CAMEL-7813

Its not really common to reply to the same queue you consumed the message from.

On Mon, Jan 12, 2015 at 4:45 AM, Minh Tran <da...@gmail.com> wrote:
> Hi
>
> It seems that when Camel replies to a message, it does not remove the JMSReplyTo header off the reply. I have looked at the unit test testSendInOnlyWithReplyTo in Camel’s unit tests and there’s a comment there that describes having to ignore this field being sent.
>
> // we should disable reply to to avoid sending the message back to our self
> // after we have consumed it
>
> This is not a good solution if the listener happens to be a separate application. They wouldn’t have any idea to ignore the JMSReplyTo header. Wouldn’t this be classified as a bug? Camel should remove this field out when replying shouldn’t it?



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2nd edition: http://www.manning.com/ibsen2