yep, you need to make the downstream route do configure multi-threading,
otherwise you will get duplicate messages
instead of this...
from("jms:topic:super_topic?concurrentConsumers=10)...
do this...
from("jms:topic:super_topic?concurrentConsumers=1&maxConcurrentConsumers=1).threads(10)...
enalposi wrote:
>
> Hi -
>
> The answer may be as simple as 'that's the way it is, but what we observe
> is not ideal:
> Basically a pool of 'listeners'
> (jms:topic:super_topic?concurrentConsumers=10) all receive the same
> message, whereas the ideal scenario would be only one thread handles each
> msg and to process different messages concurrently in the thread pool.
>
> This (obviously) works fine with queues since only one consumer can pick
> the msg off the transpor,t but we need several hosts to receive the
> payload. Is this expected behavior and we have to manage our own pool of
> async processing resources behind a single Topic listener thread?
>
> Thanks!
>
-----
Ben O'Day
IT Consultant -http://consulting-notes.com
--
View this message in context:
http://camel.465427.n5.nabble.com/Each-concurrentConsumer-on-JMS-Topic-receives-ALL-msgs-tp4558687p4558803.html
Sent from the Camel - Users mailing list archive at Nabble.com.
