Hi The behaviour you're observing has nothing to do with Camel itself but the underlying JMS-Provider [1] which has many configuration options like for the Dispatching-Policy as well.
Most probably if you would switch to another Provider (like IBM WebSphere MQ) you would observe another behaviour for which you would then consolidate it's own documentation. I hope by now it's already clear to you why message 3, 6 and 9 are delayed until message 0 has completed processing as having 3 concurrent consumer that's what Round-Rubin is expected to be :-) [1] http://activemq.apache.org/dispatch-policies.html Babak -- View this message in context: http://camel.465427.n5.nabble.com/jms-concurrentConsumers-is-not-competing-consumers-tp5455658p5485752.html Sent from the Camel - Users mailing list archive at Nabble.com.
