I have a scenario where I have multiple queues to poll, which then throttles the message into a processor (to bean). I have configured concurrent consumers in jmsConfig and comma separated queues in "from" method or tag.
During initial startup, all the pending messages in the queues are being picked up by a *single thread* and pass it over to the "to bean", even though concurrent consumers are configured. But if the messages are arrived on the go (When camel-spring setup is up and running), *multiple threads* are being used to pick the messages randomly. I would like to understand the behavior of camel against the aforesaid situation. Is it using Round-roubin to poll messages from different queues ? And if so why it is using a single thread to poll for the pending messages just after the startup ? Is there a way, so that the camel's behaviour will be uniform for both pending and incoming messages? I want my pending messages should also being consumed through multiple threads and not by a single thread Technology Stack - Spring, ApacheMQ and Apache camel Thanks in advance!! Happy Coding -- View this message in context: http://camel.465427.n5.nabble.com/Camel-is-unable-to-use-concurrent-consumers-for-polling-pending-messages-just-after-the-start-tp5781666.html Sent from the Camel - Users mailing list archive at Nabble.com.
