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 2021/03/22 14:26:00 UTC

[jira] [Updated] (CAMEL-16383) camel-scheduler - ConcurrentTasks option vs core pool size

     [ https://issues.apache.org/jira/browse/CAMEL-16383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-16383:
--------------------------------
    Summary: camel-scheduler - ConcurrentTasks option vs core pool size  (was: camel-scheduler - ConcurrentTasks option)

> camel-scheduler - ConcurrentTasks option vs core pool size
> ----------------------------------------------------------
>
>                 Key: CAMEL-16383
>                 URL: https://issues.apache.org/jira/browse/CAMEL-16383
>             Project: Camel
>          Issue Type: Improvement
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 3.10.0
>
>
> The scheduler has option concurrentTasks which is 1 by default. But if you set it to 2+ then you would have the scheduler 2+ times which is not intentional.
> What users meant to configure is the pool size, so the thread pool may have 2+ threads instead of a single as worker



--
This message was sent by Atlassian Jira
(v8.3.4#803005)