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 (Created) (JIRA)" <ji...@apache.org> on 2012/02/13 12:26:59 UTC
[jira] [Created] (SLING-2420) Prevent deadlock with Framework
Prevent deadlock with Framework
-------------------------------
Key: SLING-2420
URL: https://issues.apache.org/jira/browse/SLING-2420
Project: Sling
Issue Type: Improvement
Components: Extensions
Affects Versions: i18n 2.2.0
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: i18n 2.2.2
JcrResourceBundleProvider may cause a deadlock between itself and the OSGi Framework:
* clearCache is called from framework and synchronizes on itself while calling into the framework
* getResoureBundleInternal synchronizes on itself and calls into the framework
Fixes:
- clearCache synchronizes on self to get a copy of the service registration list and clears the list; the services are unregistered outside of the sync
- getResourceBundleInternal only stores the service registration in the internal list in the synchronized block
--
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
[jira] [Resolved] (SLING-2420) Prevent deadlock with Framework
Posted by "Felix Meschberger (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved SLING-2420.
--------------------------------------
Resolution: Fixed
Fixed in Rev. 1243476
> Prevent deadlock with Framework
> -------------------------------
>
> Key: SLING-2420
> URL: https://issues.apache.org/jira/browse/SLING-2420
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: i18n 2.2.0
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: i18n 2.2.2
>
>
> JcrResourceBundleProvider may cause a deadlock between itself and the OSGi Framework:
> * clearCache is called from framework and synchronizes on itself while calling into the framework
> * getResoureBundleInternal synchronizes on itself and calls into the framework
> Fixes:
> - clearCache synchronizes on self to get a copy of the service registration list and clears the list; the services are unregistered outside of the sync
> - getResourceBundleInternal only stores the service registration in the internal list in the synchronized block
--
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
[jira] [Closed] (SLING-2420) Prevent deadlock with Framework
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-2420.
-----------------------------------
> Prevent deadlock with Framework
> -------------------------------
>
> Key: SLING-2420
> URL: https://issues.apache.org/jira/browse/SLING-2420
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: i18n 2.2.0
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: i18n 2.2.2
>
>
> JcrResourceBundleProvider may cause a deadlock between itself and the OSGi Framework:
> * clearCache is called from framework and synchronizes on itself while calling into the framework
> * getResoureBundleInternal synchronizes on itself and calls into the framework
> Fixes:
> - clearCache synchronizes on self to get a copy of the service registration list and clears the list; the services are unregistered outside of the sync
> - getResourceBundleInternal only stores the service registration in the internal list in the synchronized block
--
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