[jira] [Updated] (SLING-4874) 'classic' jobs going via event admin get blocked

["Stefan Egli (JIRA)" <ji...@apache.org>]

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

Stefan Egli updated SLING-4874:
-------------------------------
    Attachment: SLING-4874-patch.txt

Attaching [^SLING-4874-patch.txt] provided by [~cziegeler]

> 'classic' jobs going via event admin get blocked
> ------------------------------------------------
>
>                 Key: SLING-4874
>                 URL: https://issues.apache.org/jira/browse/SLING-4874
>             Project: Sling
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: Event 3.7.0
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>             Fix For: Event 3.7.2
>
>         Attachments: SLING-4874-patch.txt
>
>
> For jobs that do not use the new job api but rather go via the classic event admin, the jobs might end up being queued until the 'Queue manager maintenance' scans through the jobs as a fallback (which by default happens every 60 seconds - so those jobs might get stuck for 60 sec).
> The problem is two fold:
> * when a job is finished it is not properly notifying the job queue
> * also, such classic jobs are not properly doing audit log, statistics update, email notification nor updating the processingJobsList appropriately (leading to statistic counting being wrong even if notification would work fine)



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