[
https://issues.apache.org/jira/browse/CAMEL-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558230#comment-13558230
]
Raul Kripalani commented on CAMEL-5974:
---------------------------------------
I reverted the changes on both branches while I drill into what's going on.
[~davsclaus], I'd like to investigate further before we take a decision. With
the current Task Executor, 8 hours of operation with very little messaging
traffic gave us a thread thrash of around 40.000 JMS threads created/destroyed
- crazy! That's why I believe this enhancement to be beneficial for folks
running on 2.10.x too.
I'll keep you updated on the next few days.
> 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
