JobEventHandler: jobs in a waiting state won't be waked up anymore if
job.getProperty(EventUtil.PROPERTY_JOB_QUEUE_NAME) != null
--------------------------------------------------------------------------------------------------------------------------------
Key: SLING-1710
URL: https://issues.apache.org/jira/browse/SLING-1710
Project: Sling
Issue Type: Bug
Components: Extensions
Affects Versions: Extensions Event 2.3.0
Reporter: Philipp Koch
Priority: Critical
it may happen that a job (before execution) is put in a waiting state because
the maximum parallel job count was reached.
unfortunately, that waiting job won't be notified anymore in case the job is
bound to a defined job queue:
1377 if ( job.getProperty(EventUtil.PROPERTY_JOB_QUEUE_NAME) == null ) {
1378 this.parallelJobCount--;
1379 this.backgroundLock.notify();
1380 }
couldn't one simply remove the
"job.getProperty(EventUtil.PROPERTY_JOB_QUEUE_NAME) == null" check or is there
a reason why this check got added?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
