[
https://issues.apache.org/jira/browse/SLING-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381789#comment-15381789
]
Chetan Mehrotra commented on SLING-5831:
----------------------------------------
bq. I'm not in favour of by default allowing all pool names and giving a way to
restrict this.
I am fine with providing a way to restrict it. Just suggesting that by default
its not restricted. If the sys admin wants he can configure a whitelist on the
setup
We anyway allow creation of threadpool without any explicit config i.e. just a
lookup call with anyname leads to creation of pool. In similar way just having
the config present in scheduled job should allow such a pool to be used.
Right now to make use of this feature we would always have to modify the
Scheduler config.
> Support different thread pools for scheduled tasks
> --------------------------------------------------
>
> Key: SLING-5831
> URL: https://issues.apache.org/jira/browse/SLING-5831
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Commons Scheduler 2.4.16
>
>
> Right now the scheduler uses a single thread pool. While this thread pool can
> be configured, it means that all scheduled tasks share this pool. In order to
> prioratize different tasks over others and avoid blocking important jobs
> through unimportant once, we could maybe add a configuration property to
> select a thread pool name.
> If a pool with that name exists, it's used - if not the default is used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
