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 2010/07/05 14:00:54 UTC
[jira] Updated: (SLING-1580) SlingServletResolver registers OSGi
services from synchronized blocks
[ https://issues.apache.org/jira/browse/SLING-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-1580:
------------------------------------
Fix Version/s: Servlets Resolver 2.0.10
> SlingServletResolver registers OSGi services from synchronized blocks
> ---------------------------------------------------------------------
>
> Key: SLING-1580
> URL: https://issues.apache.org/jira/browse/SLING-1580
> Project: Sling
> Issue Type: Bug
> Components: Servlets
> Affects Versions: Servlets Resolver 2.0.8
> Reporter: Bertrand Delacretaz
> Assignee: Carsten Ziegeler
> Priority: Minor
> Fix For: Servlets Resolver 2.0.10
>
>
> The synchronized bindServlet method calls createServlet which in turns calls context.getBundleContext().registerService(...).
> This means OSGi framework calls are done from a synchronized method, which can lead to deadlocks.
> I think we can synchronize much less, it's probably just the changes to the servletsByReference and pendingServlets collections that need to be synchronized.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.