As it's a LinkedBlockingQueue, the messages are read using BlockingQueue#poll method, then whatever the result of the processing may be, the messages has been picked.
I think the multipleConsumers acts like the multicast <http://camel.apache.org/multicast.html> processor, you could replace SEDA+multipleConsumers by SEDA+multicast and have the same result, and you could execute theses consumers in parallel (fork & join). If you have only one parallel consumer (concurrentConsumers=1) and it stalls, then the queue could fill and the producer could block or not depending on the blockWhenFull setting. This is not related to multipleConsumers settings though. -- View this message in context: http://camel.465427.n5.nabble.com/capacity-of-seda-vm-with-multipleConsumers-true-tp5742266p5742296.html Sent from the Camel - Users mailing list archive at Nabble.com.
