camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Preben Asmussen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-9460) RabbitMQ - Wonder if the consumer can use a grown/shrink thread pool
Date Wed, 30 Dec 2015 17:00:51 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075202#comment-15075202
] 

Preben Asmussen commented on CAMEL-9460:
----------------------------------------

Yeah it would also make the configuration options easier to reason about sinse it's currently
a bit unclear what the relation is between threadpoolsize and concurrentconsumers is.
I guess the threadpoolsize option could be deprecated ? 


> 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)

Mime
View raw message