You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2010/09/08 14:23:32 UTC
[jira] Created: (SLING-1736) Potential Deadlock while
registering/unregistering ResourceProvider
Potential Deadlock while registering/unregistering ResourceProvider
-------------------------------------------------------------------
Key: SLING-1736
URL: https://issues.apache.org/jira/browse/SLING-1736
Project: Sling
Issue Type: Bug
Components: JCR
Affects Versions: JCR Resource 2.0.8
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Priority: Blocker
Fix For: JCR Resource 2.0.8
Upon registration and unregistration of new resource providers EventAdmin events are posted to inform interested parties of added and removed resource providers. Unfortunately these events are posted inside a synchronized(this) block, which may lead to deadlock situations.
The solution (and right thing to do) is to post the events with the EventAdmin service outside of a synchronized block.
I consider this a critical issue which blocks the next release of this module.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-1736) Potential Deadlock while
registering/unregistering ResourceProvider
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler reassigned SLING-1736:
---------------------------------------
Assignee: Carsten Ziegeler (was: Felix Meschberger)
> Potential Deadlock while registering/unregistering ResourceProvider
> -------------------------------------------------------------------
>
> Key: SLING-1736
> URL: https://issues.apache.org/jira/browse/SLING-1736
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR Resource 2.0.8
> Reporter: Felix Meschberger
> Assignee: Carsten Ziegeler
> Priority: Blocker
> Fix For: JCR Resource 2.0.8
>
>
> Upon registration and unregistration of new resource providers EventAdmin events are posted to inform interested parties of added and removed resource providers. Unfortunately these events are posted inside a synchronized(this) block, which may lead to deadlock situations.
> The solution (and right thing to do) is to post the events with the EventAdmin service outside of a synchronized block.
> I consider this a critical issue which blocks the next release of this module.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1736) Potential Deadlock while
registering/unregistering ResourceProvider
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-1736.
-------------------------------------
Resolution: Fixed
I changed the sync blocks in revision 995023 - only add and remove operations are now inside the sync, everything else is outside
> Potential Deadlock while registering/unregistering ResourceProvider
> -------------------------------------------------------------------
>
> Key: SLING-1736
> URL: https://issues.apache.org/jira/browse/SLING-1736
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR Resource 2.0.8
> Reporter: Felix Meschberger
> Assignee: Carsten Ziegeler
> Priority: Blocker
> Fix For: JCR Resource 2.0.8
>
>
> Upon registration and unregistration of new resource providers EventAdmin events are posted to inform interested parties of added and removed resource providers. Unfortunately these events are posted inside a synchronized(this) block, which may lead to deadlock situations.
> The solution (and right thing to do) is to post the events with the EventAdmin service outside of a synchronized block.
> I consider this a critical issue which blocks the next release of this module.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.