[
https://issues.apache.org/jira/browse/CAMEL-7250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734438#comment-14734438
]
Daniel Sabag commented on CAMEL-7250:
-------------------------------------
so what is the current alternative on setting a custom threadName to a thread
pool profile.
I'm asking that because we have many routes that all (or many) uses the
threads() component taken from some profile, but each pool its using its own
name, in code:
from(a).threads().executorServiceRef("someProfile").threadName("someGroup").
now from 2.13 we cannot do that , and I am unable to find alternative.
appreciate any help given.
Thanks
Daniel
> 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.3.4#6332)
