[
https://issues.apache.org/jira/browse/CAMEL-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075154#comment-15075154
]
Claus Ibsen commented on CAMEL-9460:
------------------------------------
Looking at the code, then that executor service is only used as a boss thread
that connects to the rabbitmq broker. And as such it should just be 1 thread.
And the thread pool should be private for the consumer only, and not really
exposed in the endpoint class.
The concurrent consumers is run and handled by the rabbit mq client library and
is outside the control of that executor service.
> RabbitMQ - Wonder if the consumer can use a grown/shrink thread pool
> --------------------------------------------------------------------
>
> Key: CAMEL-9460
> URL: https://issues.apache.org/jira/browse/CAMEL-9460
> Project: Camel
> Issue Type: Improvement
> Components: camel-rabbitmq
> Reporter: Claus Ibsen
> Fix For: Future
>
>
> The consumer creates a default thread pool of 10. You can configure the size
> but the pool is fixed.
> Wonder if we should use a bounded pool so we can have min-max so it can grow
> depending on demand. That is a bit hard to do as the thread pools in jdk
> isn't so good at this.
> The spring-jms has a fair bit of logic to do this scaling up/down.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
