OrderedQueue: remove all might leave a stale entry
--------------------------------------------------

                 Key: SLING-2323
                 URL: https://issues.apache.org/jira/browse/SLING-2323
             Project: Sling
          Issue Type: Bug
          Components: Extensions
    Affects Versions: Extensions Event 3.1.0
            Reporter: Carsten Ziegeler
            Assignee: Carsten Ziegeler
             Fix For: Extensions Event 3.1.2


When remove all is called on an ordered queue while there the queue is actually 
processing a retry (sleeping), this could lead to the situation where this 
entry is causing a deadlock/stale entry in the queue. The retried job is tried 
again while just before the queue has been emptied and the queue thinks it is 
empty.
The actions need a better synchronization and the retried job needs to be 
dropped as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to