[
https://issues.apache.org/jira/browse/SLING-984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-984.
----------------------------------
Resolution: Fixed
The scheduler is now registered with a unique run id.
In revision 778362 I've also updated to the latest available quartz version
> Registered quartz scheduler should use unique name
> --------------------------------------------------
>
> Key: SLING-984
> URL: https://issues.apache.org/jira/browse/SLING-984
> Project: Sling
> Issue Type: Bug
> Components: Commons Scheduler
> Affects Versions: Commons Scheduler 2.0.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Commons Scheduler 2.0.6
>
>
> The registered quartz scheduler always uses the default scheduler name -
> which results in problems if - for whatever reason - the deactivate method
> (and therefore the unregistering) hasn't been called or if the bundle is
> running more than once.
> Quartz does not allow to register the same scheduler name more than once. It
> seems - although the library is embedded in the bundle - that this name is
> registered somewhere outside of the bundle scope which therefore causes these
> problems.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
