[ https://issues.apache.org/jira/browse/SLING-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426675#comment-13426675 ]
Carsten Ziegeler commented on SLING-2535: ----------------------------------------- Actually calling shutdown on the quartz scheduler should remove the thread group. Maybe we need do to something additional > QuartzScheduler:ApacheSling thread group remaining after stopping the > scheduler bundle > -------------------------------------------------------------------------------------- > > Key: SLING-2535 > URL: https://issues.apache.org/jira/browse/SLING-2535 > Project: Sling > Issue Type: Bug > Components: Commons > Affects Versions: Commons Scheduler 2.3.4 > Reporter: Felix Meschberger > > When the Scheduler bundle is stopped, the threads (probably the thread pool) > is cleaned away but the thread group "QuartzScheduler:ApacheSling" remains. > For ultimate cleanup, I would think the thread group should also be destroyed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira