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

Henryk Konsek resolved CAMEL-7250.
----------------------------------

    Resolution: Fixed

Fixed in 87105eee5c303af4751661af9480d4a76223b01b.

> In Threads DSL thread pool options and executorServiceRef should be mutually 
> exclusive
> --------------------------------------------------------------------------------------
>
>                 Key: CAMEL-7250
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7250
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Henryk Konsek
>            Assignee: Henryk Konsek
>             Fix For: 2.13.0
>
>
> When {{executorServiceRef}} option is set on the Threads DSL, we should not 
> let users to set pool profile options ({{poolSize}}, {{maxQueueSize}}, etc) 
> at the same time. When {{executorServiceRef}} is set on Threads DSL, 
> mentioned options are ignored as referred {{ExecutorService}} uses its own 
> settings.
> Users tend to think that they can override thread profile options of referred 
> {{ExecutorService}} on the Threads DSL level. We should validate DSL to make 
> Threads DSL thread pool options and {{executorServiceRef}} mutually exclusive.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to