[
https://issues.apache.org/jira/browse/SLING-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381783#comment-15381783
]
Carsten Ziegeler commented on SLING-5831:
-----------------------------------------
[~chetanm] Step #1 is optional. If a pool with a name is not configured yet,
thread pool manager creates it and uses the default configuration.
I'm not in favour of by default allowing all pool names and giving a way to
restrict this. This is easily overlooked and easily abused. If your code needs
a separate thread pool this is a conscious decision and therefore I think it
makes sense that it requires some steps to configure it
> 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)
