[
https://issues.apache.org/jira/browse/SLING-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-3840.
-------------------------------------
Resolution: Fixed
Resolved in rev 1617529 by registering a service factory for the scheduler
service and adding the bundle id to registered jobs
If a bundle is stopped (bundle event), all jobs belonging to this bundle are
stopped
> Stop jobs started through the scheduler api when the client bundle stops
> ------------------------------------------------------------------------
>
> Key: SLING-3840
> URL: https://issues.apache.org/jira/browse/SLING-3840
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Commons Scheduler 2.4.4
>
>
> Right now, jobs started by a client bundle through the Scheduler API continue
> to run if that bundle is stopped and does not properly cleanup. Apart from
> memory leaks this will cause other problems as the bundle is not active
> anymore.
> Those jobs should be stopped on bundle stop in any case
--
This message was sent by Atlassian JIRA
(v6.2#6252)
