[
https://issues.apache.org/jira/browse/CAMEL-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raul Kripalani reopened CAMEL-5974:
-----------------------------------
[~bvahdat] - sure. Thanks a lot for the heads-up! I find this strange, because
I found it to work on my test system. The regression seems to only affect only
InOut invocations. I hope I'll find the time tomorrow to fix it.
> camel-jms: Make ThreadPoolTaskExecutor the default Task Executor
> ----------------------------------------------------------------
>
> Key: CAMEL-5974
> URL: https://issues.apache.org/jira/browse/CAMEL-5974
> Project: Camel
> Issue Type: Improvement
> Components: camel-jms
> Reporter: Raul Kripalani
> Assignee: Raul Kripalani
> Fix For: 2.10.4, 2.11.0
>
>
> {{DefaultJmsMessageListenerContainer}} uses
> {{org.springframework.core.task.SimpleAsyncTaskExecutor}} as the default task
> executor.
> This causes a lot of thread thrash when setting a positive
> idleTaskExecutionLimit. New threads are created every time the consumers are
> refreshed, i.e. closed down and started again to keep the minimum number of
> them around (= concurrentConsumers).
> Replace with
> {{org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor}} instead,
> with the following config:
> * corePoolSize = concurrentConsumers
> * maxPoolSize = maxConcurrentConsumers
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
