[
https://issues.apache.org/jira/browse/SLING-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904599#action_12904599
]
Philipp Koch commented on SLING-1710:
-------------------------------------
btw. this got logged before the job got put asleep:
30.08.2010 13:17:20.016 WARN [pool-3-thread-3]
org.apache.sling.event.impl.JobEventHandler Unable to create new job queue
named com/day/cq/workflow/job/etc/workflow/models/dam/update_asset as there are
already 10 job queues. Try to increase the maximum number of job queues!
...
...
30.08.2010 13:17:20.243 *DEBUG* [pool-3-thread-4]
org.apache.sling.event.impl.JobEventHandler Executing job
org.osgi.service.event.Event(1906682309) [topic=org/apache/sling/event/job,
properties=event.job.retries=3,event.job.topic=com/day/cq/workflow/job/etc/workflow/models/dam/update_asset,event.topics=org/apache/sling/event/job,com.day.cq.workflow.job=com.day.cq.workflow.job.workflow...@375cb0ef,com.day.cq.workflow.jobid=VolatileWorkItem_node3_etc_workflow_instances_2010-08-30_update_asset_9566822167534923,event.job.parallel=48,event.job.queuename=com/day/cq/workflow/job/etc/workflow/models/dam/update_asset].
30.08.2010 13:17:20.243 *DEBUG* [pool-3-thread-4]
org.apache.sling.event.impl.JobEventHandler Waiting with executing job
org.osgi.service.event.Event(1906682309) [topic=org/apache/sling/event/job,
properties=event.job.retries=3,event.job.topic=com/day/cq/workflow/job/etc/workflow/models/dam/update_asset,event.topics=org/apache/sling/event/job,com.day.cq.workflow.job=com.day.cq.workflow.job.workflow...@375cb0ef,com.day.cq.workflow.jobid=VolatileWorkItem_node3_etc_workflow_instances_2010-08-30_update_asset_9566822167534923,event.job.parallel=48,event.job.queuename=com/day/cq/workflow/job/etc/workflow/models/dam/update_asset]
- maximum parallel job count of 15 reached!
means the job in question got put into the main queue but the job name property
got not cleared.
> 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.
