camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: Each concurrentConsumer on JMS Topic receives ALL msgs
Date Thu, 07 Jul 2011 16:10:33 GMT
The JmsConsumer will wait for the Exchange to complete.

There is a ticket to improve this by supporting the async routing
engine on the consumer level for InOnly JMS consumers.

On Thu, Jul 7, 2011 at 6:01 PM, enalposi <> wrote:
> Hi Tim -
> Using Camel 2.7.2.
> I actually had the ExchangePattern before threads() originally - the above
> is just one permutation of several I tried (just moved it back - same
> result).
> Yes, I guess it should block if the 'consumer'/publisher is expecting a
> response. But it's using OutOnly ExchangePattern. Additionally I set
> disableReplyTo=true which Claus pointed out in some other post to really
> make this one-directional.
> Regarding ack - shouldn't in this configuration the ack be returned by the
> jms consumer thread, before handing it over to the worker thread pool? From
> what I read it defaults to AUTO_ACKNOWLEDGE. I opened up both Camel and
> Spring with DEBUG log level but see nothing related. On the Camel API side I
> am not sure how to get a handle on anything to acknowledge given the
> transport agnostic level of abstraction if I wanted to try out CLIENT_ACK.
> Cheers.
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

Claus Ibsen
Twitter: davsclaus, fusenews
Author of Camel in Action:

View raw message