Hi Claus, Thank you for pointing out that I needed the "concurrentConsumers" parameter to my endpoint URI - that's a little hidden I must say(!). As a relative newcomer I would have thought that the "thread" method be the thing to use.
Would it be a useful enhancement to have the thread method set the concurrentConsumers property where the endpoint is derived from jms, or does that pollute the code? Kind regards, Christopher -- View this message in context: http://www.nabble.com/activemq-endpoint-and-thread-pools-tp20187089s22882p20195390.html Sent from the Camel - Users mailing list archive at Nabble.com.
