[
https://issues.apache.org/jira/browse/CAMEL-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558094#comment-13558094
]
Babak Vahdat commented on CAMEL-5974:
-------------------------------------
This fix causes more than 100 camel-jms unit-tests to fail:
https://builds.apache.org/job/Camel.trunk.fulltest/1195/org.apache.camel$camel-jms/#showFailuresLink
Reverting back the change of this ticket on my workspace makes *all* the
camel-jms tests to pass again!
It also causes test failure by other Maven modules as well:
https://builds.apache.org/job/Camel.trunk.fulltest/1195/org.apache.camel$camel-example-loan-broker/testReport/org.apache.camel.loanbroker.queue.version/LoanBrokerQueueTest/testClientInvocation/
Again reverting back r1433767 on my workspace would make this test to pass
again.
Could you please take a look at this?
> 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
