[
https://issues.apache.org/jira/browse/SLING-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488220#comment-13488220
]
Ian Boston commented on SLING-2535:
-----------------------------------
Hmm, I see what you mean.
The shutdown in decUsage has the potential to cause a deadlock.
public void decUsage() {
synchronized (usagelock) {
this.count--;
if ( this.count == 0 ) {
this.shutdown();
}
}
}
could be
public void decUsage() {
boolean shutdown = false;
synchronized (usagelock) {
this.count--;
if ( this.count == 0 ) {
shutdown = true;
}
}
if ( shutdown ) {
this.shutdown();
}
}
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
