You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2013/06/06 14:32:21 UTC

[jira] [Resolved] (SLING-2535) QuartzScheduler:ApacheSling thread group remaining after stopping the scheduler bundle

     [ https://issues.apache.org/jira/browse/SLING-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-2535.
-------------------------------------

    Resolution: Fixed

I think we can close this now
                
> 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
>            Assignee: Ian Boston
>             Fix For: Commons Scheduler 2.3.6
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira