[ https://issues.apache.org/jira/browse/SLING-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-339: ----------------------------------- Priority: Blocker (was: Major) Affects Version/s: Extensions Event 2.0.2 Fix Version/s: Extensions Event 2.0.4 Assignee: Carsten Ziegeler Especially, if jobs can't be run in parallel, the first job without a processor stops further processing of these jobs as the finishedJob() method is never called. This can especially happen on startup, when the event listeners haven't been registered yet. > Implement job acknowledge > ------------------------- > > Key: SLING-339 > URL: https://issues.apache.org/jira/browse/SLING-339 > Project: Sling > Issue Type: Improvement > Components: Event > Affects Versions: Extensions Event 2.0.2 > Reporter: Carsten Ziegeler > Assignee: Carsten Ziegeler > Priority: Blocker > Fix For: Extensions Event 2.0.4 > > Original Estimate: 0h > Remaining Estimate: 0h > > Currently there is no acknowledge that someone is interested in processing a > job. This results in the problem > that jobs might end up locked in the repository for ever if there is noone > interested in processing this kind of > job. > This couldbe solved by requiring that a job processor acknowledges the > receival of a job and thereby indicates that it will process this job. This > could also be used to deny other processors for this job. > If a job is not acknowledged during a specified timeout, the job will be > removed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.