Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: neutral (nike.apache.org: 216.139.236.158 is neither permitted
 nor denied by domain of k.szczesny@gmail.com)
Date: Mon, 8 Nov 2010 05:06:07 -0800 (PST)
From: Krystian <k.szczesny@gmail.com>
To: users@camel.apache.org
Message-ID: <1289221567150-3255019.post@n5.nabble.com>
In-Reply-To: <AANLkTinxdkNGPXY2M5Ppyjb0kKgQhhRNJ14zXRsefmZi@mail.gmail.com>
References: <1289178017146-3254431.post@n5.nabble.com>
 <AANLkTi=fQxwxf7oYKBbHRHEMHrwRnA3PuoE0k2GENzZ1@mail.gmail.com>
 <1289209514111-3254779.post@n5.nabble.com>
 <AANLkTinxdkNGPXY2M5Ppyjb0kKgQhhRNJ14zXRsefmZi@mail.gmail.com>
Subject: Re: Cannot reply to a message routed by camel
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


It all seems like it's a workaround rather than a fix.
I mean... the olution I've got right now is simple and works fine with this
one small issue: reply-to queue being changed.
Since reply-to queues are changing I believe new ones are created. I'm not
sure if that's the case. I cannot see anything in the debug logs, whether
there's a queue created or not. That's the mystery. How come reply to queue
changes between routed messages. To be honest I thought it would be the same
message rerouted all the time with some additional camel-only properties
appended to the body. It seems [again] this is not the case.

So... to recap.
I'm not willing to change the process now [before I see that there's no
other option] as all the changes seem to me like resource hogs in situation
of let's say 100 000 clients. Different listener groups would mean that the
order of messages could get screwed up [at least more screwed up than in
original solution].

Any ideas?

Thanks,
Krystian
-- 
View this message in context: http://camel.465427.n5.nabble.com/Cannot-reply-to-a-message-routed-by-camel-tp3254431p3255019.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.