[ https://issues.apache.org/jira/browse/SLING-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378134#comment-15378134 ]
Carsten Ziegeler commented on SLING-5831: ----------------------------------------- As a first step I've refactored the code and created a SchedulerProxy which is holding the quartz scheduler and the corresponding thread pool. If we agree that this is the way to go, we can simply create a map with those proxies based on the thread pool name > 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 > 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)