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 2016/09/02 16:30:20 UTC

[jira] [Reopened] (SLING-6030) Unscheduling Cron-Jobs does not work

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

Carsten Ziegeler reopened SLING-6030:
-------------------------------------

> Unscheduling Cron-Jobs does not work
> ------------------------------------
>
>                 Key: SLING-6030
>                 URL: https://issues.apache.org/jira/browse/SLING-6030
>             Project: Sling
>          Issue Type: Bug
>          Components: Commons
>    Affects Versions: Event 4.0.0
>         Environment: AEM-6.2
>            Reporter: Henry Krause
>              Labels: events
>         Attachments: crontest.tar
>
>
> Unscheduling a scheduled (cron-) Job is not being persisted. Therefore old cron jobs reappear after some time. Events are fired multiple times.
> I encountered this bug with AEM-6.2. Cronjobs are unusable this way. I must remove corresponding nodes under /var/eventing/scheduled-jobs to get rid of them.
> Please notice attached simple app with two components. CronScheduler should schedule/unschedule 1 cron job on activation/deactivation. CronProcessor simply consumes the events and logs.
> When manually deactivating the CronScheduler-Component all seems fine in the first place, but after some time old cron-jobs reappear for they have never been removed from the repository.
> To reproduce deactivate/activate the CronScheduler-Component some times and you get multiple instances of the same cron-Job.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)