camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ShlomiJ <shlomij...@gmail.com>
Subject Re: Threads not consuming in parallel
Date Tue, 14 Feb 2012 14:23:17 GMT
*Solved!* sort of...

The problem was that the JMS queue got filled with messages *before* any
consumer was available.

When the consumers were finally started, by initiating the to:activemq
endpoint, all existing messages in the JMS queue were assigned to a *single
consumer!*

That caused the _appearance_ of a sequential processing, while actually
*new* messages WERE distributed among consumers evenly and were passed in
parallel, each to a different thread in the pool.

to Willem.Jiang:

Willem.Jiang wrote
> Did you have a change to set the activemq endpoint option of 
> concurrentConsumers like this? 
> 
> 
I've tried it, but it simply overrides the corresponding JmsConfiguration's
properties from the camel-context.xml. It did not changed anything.

Now I realize that a consumer is attached to a thread from the pool, until
that thread is finished.
Why?

*Can't a consumer simply pass a message to a thread from the pool and be
done with it, without having to wait for the thread to finish it run?*

any thoughts?

ShlomiJ



--
View this message in context: http://camel.465427.n5.nabble.com/Threads-not-consuming-in-parallel-tp5482274p5482568.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message