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: http://camel.465427.n5.nabble.com/Each-concurrentConsumer-on-JMS-Topic-receives-ALL-msgs-tp4558687p4561538.html Sent from the Camel - Users mailing list archive at Nabble.com.
