You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Raul Kripalani (JIRA)" <ji...@apache.org> on 2013/01/16 01:36:13 UTC
[jira] [Commented] (CAMEL-5974) camel-jms: Make
ThreadPoolTaskExecutor the default Task Executor
[ https://issues.apache.org/jira/browse/CAMEL-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13554571#comment-13554571 ]
Raul Kripalani commented on CAMEL-5974:
---------------------------------------
Fixed in trunk in r1433767, and 2.10.x branch in r1433765.
> 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