You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Jonathan Anstey (Created) (JIRA)" <ji...@apache.org> on 2011/11/02 14:31:32 UTC
[jira] [Created] (CAMEL-4606) Set custom threadpool for aggregator
background tasks
Set custom threadpool for aggregator background tasks
-----------------------------------------------------
Key: CAMEL-4606
URL: https://issues.apache.org/jira/browse/CAMEL-4606
Project: Camel
Issue Type: Improvement
Affects Versions: 2.8.2
Reporter: Jonathan Anstey
Assignee: Jonathan Anstey
Fix For: 2.9.0
Right now if you use either of the completionTimeout, completionTimeoutExpression, or completionInterval features of the aggregator a background thread is created to check for the completion. If you have a 100 routes with aggregators say, you will have 100 background threads created... kinda sucky for scalability... we should allow users to set a thread pool to use for these background threads as well. Right now, we only allow setting an executor service for the main aggregation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-4606) Set custom threadpool for aggregator
background tasks
Posted by "Jonathan Anstey (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Anstey resolved CAMEL-4606.
------------------------------------
Resolution: Fixed
> Set custom threadpool for aggregator background tasks
> -----------------------------------------------------
>
> Key: CAMEL-4606
> URL: https://issues.apache.org/jira/browse/CAMEL-4606
> Project: Camel
> Issue Type: Improvement
> Affects Versions: 2.8.2
> Reporter: Jonathan Anstey
> Assignee: Jonathan Anstey
> Fix For: 2.9.0
>
>
> Right now if you use either of the completionTimeout, completionTimeoutExpression, or completionInterval features of the aggregator a background thread is created to check for the completion. If you have a 100 routes with aggregators say, you will have 100 background threads created... kinda sucky for scalability... we should allow users to set a thread pool to use for these background threads as well. Right now, we only allow setting an executor service for the main aggregation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira