camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raul Kripalani (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-5974) camel-jms: Make ThreadPoolTaskExecutor the default Task Executor
Date Wed, 16 Jan 2013 00:36:12 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Raul Kripalani updated CAMEL-5974:
----------------------------------

    Fix Version/s:     (was: 2.9.6)
    
> 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

Mime
View raw message