You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Philipp Koch (JIRA)" <ji...@apache.org> on 2009/05/29 15:04:45 UTC
[jira] Created: (SLING-987) Jobs/Events are purged in an
uncontrolled way
Jobs/Events are purged in an uncontrolled way
---------------------------------------------
Key: SLING-987
URL: https://issues.apache.org/jira/browse/SLING-987
Project: Sling
Issue Type: Bug
Components: Event
Reporter: Philipp Koch
Priority: Blocker
We already had this problem for pretty big event/job queues once (a month ago or so. could not find a jira issue) that the job in the queue got purged because the "job acknowledge" timed out for that job (by default the job/event is purged after 3 timeouts). the above mentioned fix fixed the issue quite well. it appeared now again when running such big queues on very fast boxes:
9.05.2009 13:00:07.904 *INFO* [pool-4-thread-1] org.apache.sling.event.impl.JobEventHandler No acknowledge received for job org.osgi.service.event.Event [topic=com/day/cq/workflow/job] stored at /var/eventing/jobs/com.day.cq.workflow.job/Job5a50f993-8f36-4eae-81d5-3124ca455bf5. Requeueing job.
the funny thing is now that the timeout does not happen after hours but already after 10 mins. there are no (debug) log entries that would point to some event handler problems...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-987) Jobs/Events are purged in an
uncontrolled way
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718372#action_12718372 ]
Carsten Ziegeler commented on SLING-987:
----------------------------------------
I've set the queue size to unlimited in Revision 783711
> Jobs/Events are purged in an uncontrolled way
> ---------------------------------------------
>
> Key: SLING-987
> URL: https://issues.apache.org/jira/browse/SLING-987
> Project: Sling
> Issue Type: Bug
> Components: Event
> Affects Versions: Extensions Event 2.0.4
> Reporter: Philipp Koch
> Assignee: Carsten Ziegeler
> Priority: Blocker
> Fix For: Extensions Event 2.0.6
>
>
> We already had this problem for pretty big event/job queues once (a month ago or so. could not find a jira issue) that the job in the queue got purged because the "job acknowledge" timed out for that job (by default the job/event is purged after 3 timeouts). the above mentioned fix fixed the issue quite well. it appeared now again when running such big queues on very fast boxes:
> 9.05.2009 13:00:07.904 *INFO* [pool-4-thread-1] org.apache.sling.event.impl.JobEventHandler No acknowledge received for job org.osgi.service.event.Event [topic=com/day/cq/workflow/job] stored at /var/eventing/jobs/com.day.cq.workflow.job/Job5a50f993-8f36-4eae-81d5-3124ca455bf5. Requeueing job.
> the funny thing is now that the timeout does not happen after hours but already after 10 mins. there are no (debug) log entries that would point to some event handler problems...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-987) Jobs/Events are purged in an
uncontrolled way
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler reassigned SLING-987:
--------------------------------------
Assignee: Carsten Ziegeler
> Jobs/Events are purged in an uncontrolled way
> ---------------------------------------------
>
> Key: SLING-987
> URL: https://issues.apache.org/jira/browse/SLING-987
> Project: Sling
> Issue Type: Bug
> Components: Event
> Reporter: Philipp Koch
> Assignee: Carsten Ziegeler
> Priority: Blocker
>
> We already had this problem for pretty big event/job queues once (a month ago or so. could not find a jira issue) that the job in the queue got purged because the "job acknowledge" timed out for that job (by default the job/event is purged after 3 timeouts). the above mentioned fix fixed the issue quite well. it appeared now again when running such big queues on very fast boxes:
> 9.05.2009 13:00:07.904 *INFO* [pool-4-thread-1] org.apache.sling.event.impl.JobEventHandler No acknowledge received for job org.osgi.service.event.Event [topic=com/day/cq/workflow/job] stored at /var/eventing/jobs/com.day.cq.workflow.job/Job5a50f993-8f36-4eae-81d5-3124ca455bf5. Requeueing job.
> the funny thing is now that the timeout does not happen after hours but already after 10 mins. there are no (debug) log entries that would point to some event handler problems...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-987) Jobs/Events are purged in an
uncontrolled way
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-987:
-----------------------------------
Affects Version/s: Extensions Event 2.0.4
Fix Version/s: Extensions Event 2.0.6
It seems that this problem is caused by massive job events being sent from the event admin - the current thread pool used for the eventing has a maximum queue size of 50; as soon as this limit is reached
the request for putting something into the queue is blocked until a place gets available inside the queue.
> Jobs/Events are purged in an uncontrolled way
> ---------------------------------------------
>
> Key: SLING-987
> URL: https://issues.apache.org/jira/browse/SLING-987
> Project: Sling
> Issue Type: Bug
> Components: Event
> Affects Versions: Extensions Event 2.0.4
> Reporter: Philipp Koch
> Assignee: Carsten Ziegeler
> Priority: Blocker
> Fix For: Extensions Event 2.0.6
>
>
> We already had this problem for pretty big event/job queues once (a month ago or so. could not find a jira issue) that the job in the queue got purged because the "job acknowledge" timed out for that job (by default the job/event is purged after 3 timeouts). the above mentioned fix fixed the issue quite well. it appeared now again when running such big queues on very fast boxes:
> 9.05.2009 13:00:07.904 *INFO* [pool-4-thread-1] org.apache.sling.event.impl.JobEventHandler No acknowledge received for job org.osgi.service.event.Event [topic=com/day/cq/workflow/job] stored at /var/eventing/jobs/com.day.cq.workflow.job/Job5a50f993-8f36-4eae-81d5-3124ca455bf5. Requeueing job.
> the funny thing is now that the timeout does not happen after hours but already after 10 mins. there are no (debug) log entries that would point to some event handler problems...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-987) Jobs/Events are purged in an
uncontrolled way
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-987.
----------------------------------
Resolution: Fixed
> Jobs/Events are purged in an uncontrolled way
> ---------------------------------------------
>
> Key: SLING-987
> URL: https://issues.apache.org/jira/browse/SLING-987
> Project: Sling
> Issue Type: Bug
> Components: Event
> Affects Versions: Extensions Event 2.0.4
> Reporter: Philipp Koch
> Assignee: Carsten Ziegeler
> Priority: Blocker
> Fix For: Extensions Event 2.0.6
>
>
> We already had this problem for pretty big event/job queues once (a month ago or so. could not find a jira issue) that the job in the queue got purged because the "job acknowledge" timed out for that job (by default the job/event is purged after 3 timeouts). the above mentioned fix fixed the issue quite well. it appeared now again when running such big queues on very fast boxes:
> 9.05.2009 13:00:07.904 *INFO* [pool-4-thread-1] org.apache.sling.event.impl.JobEventHandler No acknowledge received for job org.osgi.service.event.Event [topic=com/day/cq/workflow/job] stored at /var/eventing/jobs/com.day.cq.workflow.job/Job5a50f993-8f36-4eae-81d5-3124ca455bf5. Requeueing job.
> the funny thing is now that the timeout does not happen after hours but already after 10 mins. there are no (debug) log entries that would point to some event handler problems...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.