[
https://issues.apache.org/jira/browse/CAMEL-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15080419#comment-15080419
]
Preben Asmussen commented on CAMEL-9460:
----------------------------------------
Here is a proposed patch
https://github.com/pax95/camel/commit/56c5ba20e768883db75e68092603c7449be1d191
To me it seems reasonable that the threadpool is allocated = the number of
concurrent consumers(open channels), but since I'm not a Rabbit user myself,
maybe a Rabbit user has some comments.
Btw I have removed the threadPoolSize option. I'm not sure if you can remove
options in major versions, or if they should be deprecated instead.
> 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)
