[
https://issues.apache.org/jira/browse/SLING-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676061#comment-13676061
]
Carsten Ziegeler commented on SLING-2906:
-----------------------------------------
I've committed a first implementation in rev 1489934 - it uses a new flag which
is set to false if the queue is not waiting for a new job. As long as this flag
is set to false, the queue will not be marked for closing.
In addition I simplified the handling of closing a queue by moving it
completely into the queue (tryToClose())
> Queue might be outdated and closed while still processing
> ---------------------------------------------------------
>
> Key: SLING-2906
> URL: https://issues.apache.org/jira/browse/SLING-2906
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Extensions Event 3.1.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Extensions Event 3.2.0
>
>
> Though this might rarely happen, there is a potential that a queue gets
> outdated and closed although it's still processing:
> There is a little time window, once the last job is taken from the queue
> until the processing starts - during this window, the queue is empty and the
> list of jobs in processing is empty as well. If the call for marking the
> queue arrives during exactly this window, the queue will be outdated. Now if
> the next call to close the queue arrives in a similar window, the queue will
> be closed although there are still jobs in processing
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
