You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2011/01/26 19:52:44 UTC
[jira] Resolved: (SLING-1957) Potential deadlock when queue is
suspended and resumed
[ https://issues.apache.org/jira/browse/SLING-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-1957.
-------------------------------------
Resolution: Fixed
Added explicit syncs for the suspend state and changed the invocation order in the queue run method to avoid any processing when the queue is suspended.
> Potential deadlock when queue is suspended and resumed
> ------------------------------------------------------
>
> Key: SLING-1957
> URL: https://issues.apache.org/jira/browse/SLING-1957
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Extensions Event 3.0.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Extensions Event 3.0.2
>
>
> If a queue is suspended there is a potential that the queue stays in the suspended state when it gets resumed.
> This is because the notify waking up the thread is done before the state is set to resumed
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.