Hi. According to the camel scheduler documentation it is possible to configure its threadpool to support more than one thread at a time. According to the following commit <http://mail-archives.apache.org/mod_mbox/camel-commits/201502.mbox/%3cab29b22c34b342c596433209c2702...@git.apache.org%3E> the option for it is "concurrentTasks=<int>".
However when I apply this option and use the debugger I see that the configured number of threads are created but the scheduler always uses one thread only, i.e. if I set a breakpoint in the corresponding bean method and thus make the thread wait until after the next polling interval has reached, I expect another thread to get activated and call the bean method but this does not happen. Actually the additional threads NEVER get invoked, they are just created. So one of my questions is: what is the intention behind concurrent tasks in the scheduler? Also, is it possible to achieve the desired behavior using camel scheduler or any other component? Thank you in advance -- View this message in context: http://camel.465427.n5.nabble.com/Camel-scheduler-is-not-concurrent-tp5781066.html Sent from the Camel - Users mailing list archive at Nabble.com.
