Thanks Claus - In the meantime, do you have an opinion how to work around it? I see two options (a) go via concurrentConsumers and somehow filter duplicate messages or (b) hand the payload off to a custom async worker thread pool. (a) seems to be quicker to do but not so sure about the overhead of handling all the dupe messages before it hits the filtering logic.
Thanks. -- View this message in context: http://camel.465427.n5.nabble.com/Each-concurrentConsumer-on-JMS-Topic-receives-ALL-msgs-tp4558687p4561645.html Sent from the Camel - Users mailing list archive at Nabble.com.
