[ https://issues.apache.org/jira/browse/SLING-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385366#comment-15385366 ]
Carsten Ziegeler commented on SLING-5831: ----------------------------------------- If removeJob did not throw in previous versions, this was clearly a bug. I know that it did so in the early versions and the API clearly states that removeJob throws. So I think we're totaly fine and callers of removeJob must except that exception. Can we consider this issue done? > 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 > Labels: docs-impacting > 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)