[jira] [Comment Edited] (CAMEL-5974) camel-jms: Make ThreadPoolTaskExecutor the default Task Executor

["Raul Kripalani (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569948#comment-13569948 ] 

Raul Kripalani edited comment on CAMEL-5974 at 2/4/13 2:19 AM:
---------------------------------------------------------------

Finally decided to create an option called 'defaultTaskExecutorType' which can take values SimpleAsync or ThreadPool, depending on the Task Executor type to use. Backwards functionality is preserved when this option is not specified.
                
      was (Author: raulvk):
    Finally decided to create an option called 'defaultTaskExecutorType' which can take values SimpleAsync or ThreadPool, depending on the Task Executor type to use. Backwards functionality is preserved.
                  
> 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