You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2012/10/22 10:18:12 UTC
[jira] [Created] (CAMEL-5725) Thread pool profile - maxQueueSize =
0 should mean no work queue in use
Claus Ibsen created CAMEL-5725:
----------------------------------
Summary: Thread pool profile - maxQueueSize = 0 should mean no work queue in use
Key: CAMEL-5725
URL: https://issues.apache.org/jira/browse/CAMEL-5725
Project: Camel
Issue Type: Improvement
Components: camel-core
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 2.11.0
This allows people to disable the worker queue, and thus only use direct-hand-off to the threads from the pool.
Currently 0 or -1 means unbounded worker queue. Which IMHO is not ideal as you dont want a system that can accept any new tasks in an internal memory worker queue. So IMHO we should switch 0 and -1 to be direct-hands-off. And never use unbounded queues. People can specify a Integer.MAX_SIZE which is also unbounded queue anyway.
--
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
[jira] [Resolved] (CAMEL-5725) Thread pool profile - maxQueueSize =
0 should mean no work queue in use
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-5725.
--------------------------------
Resolution: Fixed
> Thread pool profile - maxQueueSize = 0 should mean no work queue in use
> -----------------------------------------------------------------------
>
> Key: CAMEL-5725
> URL: https://issues.apache.org/jira/browse/CAMEL-5725
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.11.0
>
>
> This allows people to disable the worker queue, and thus only use direct-hand-off to the threads from the pool.
> Currently 0 or -1 means unbounded worker queue. Which IMHO is not ideal as you dont want a system that can accept any new tasks in an internal memory worker queue. So IMHO we should switch 0 and -1 to be direct-hands-off. And never use unbounded queues. People can specify a Integer.MAX_SIZE which is also unbounded queue anyway.
--
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