Ok. The behavior you are seeing makes sense to me if the consumer is waiting for a 'response'. I haven't looked at the code but there could be several reasons for this in my mind. 1. Can you check the ack mode that you have on the topic? 2. Can you move the setting of the exchange pattern up to before the threads?
You can do this in 2 ways. simply move that call or: jms:topic:super-topic?exchangePattern=InOnly Also, what version of Camel is this? -Tim On Thu, Jul 7, 2011 at 9:34 AM, enalposi <enalp...@yahoo.com> wrote: > Hey Tim. > > Sorry, I have everything parameterized and missed a few values. The > ExchangePattern is InOnly (system exposes same behavior for OutOnly for > what > it's worth...). sleepTime is constant 1000 in this case - you see nicely in > the log how threads have a 1sec gap between ''start' and 'end' log and > different worker threads from the pool are sequentially picked up. > > I initially observed this behavior on queues until figuring out that > threads(...) != concurrentConsumers... > But even for queues I am suspicious... if I for example set > concurrentConsumers=5 and threads(1) it will process sequentially. I would > have assumed the concurrentConsumer threads would automatically > multi-thread > downstream but this is not the case. I have to set both concurrencConsumers > and threads(...) to the same number to achieve concurrency. > > Based on these observations I either suspect a bug in the Camel worker > thread pool code or ignorance on my behalf how to use it correctly :-) > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Each-concurrentConsumer-on-JMS-Topic-receives-ALL-msgs-tp4558687p4561235.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
