Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4D37D971.2060609@nanthrax.net>
Date: Thu, 20 Jan 2011 07:42:57 +0100
From: =?ISO-8859-1?Q?Jean-Baptiste_Onofr=E9?= <jb@nanthrax.net>
Reply-To: jb@nanthrax.net
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.9.1.16) Gecko/20101227 Icedove/3.0.11
MIME-Version: 1.0
To: dev@camel.apache.org
Subject: Re: [DISCUSS] - JMSReplyTo to yourself
References: <AANLkTi=PVzFSa5s+bZoy34K1XhDCWT7733Vnn0QXXzo4@mail.gmail.com>
In-Reply-To: <AANLkTi=PVzFSa5s+bZoy34K1XhDCWT7733Vnn0QXXzo4@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Claus,

most of the time, we have a REQUEST queue and a RESPONSE queue.
I've never seen a response post on the same queue.

By default, it makes sense to log a WARN when posting on the same queue.
The use of disableReplyTo is too restrictive because the users could use 
a replyTo to another queue :)

Regards
JB

On 01/20/2011 07:38 AM, Claus Ibsen wrote:
> Hi
>
> Suppose you have a Camel route
>
> from("activemq:queue:foo")
>     .process(xxx)
>
> And a client sends a message to the foo queue with a JMSReplyTo header
> set with the queue:foo destination.
> The client has essentially told to send a reply back to the same queue
> as the message was consumed.
>
> Currently Camel will happily comply and send a reply message to the
> foo queue. Now what could happen is the message will keep doing this.
>
> Is there any use-cases in the real life where you want to send a reply
> message back to the same message queue?
> If not we can implement logic to detect this and avoid doing that.
> Camel can log a WARN when it has detect this so
> end users can notice in the logs if they have such a case.
>
> We can introduce an option so people can turn this odd behavior on and
> allow to send back replies to same queue.
>
>
> The current remedy is to enable this option as follows:
>
> from("activemq:queue:foo?disableReplyTo=true")
>     .process(xxx)
>
> But that's general so if there was a JMSReplyTo header with the
> queue:bar then it would be ignored as well.
> However sending to a bar queue may be a valid use-case.
>
>
>
>