[
https://issues.apache.org/jira/browse/SLING-8187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Sedding resolved SLING-8187.
-----------------------------------
Resolution: Fixed
Fix Version/s: Engine 2.6.18
> Deadlock in SlingMainServlet after SLING-8051
> ---------------------------------------------
>
> Key: SLING-8187
> URL: https://issues.apache.org/jira/browse/SLING-8187
> Project: Sling
> Issue Type: Improvement
> Components: Engine
> Affects Versions: Engine 2.6.16
> Reporter: Julian Sedding
> Assignee: Julian Sedding
> Priority: Major
> Fix For: Engine 2.6.18
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> The fix for SLING-8051 moved registration of the {{SlingServletContext}}
> instance from {{SlingMainServlet#activate()}} to {{SlingMainServlet#init()}}.
> It turns out that this can cause a deadlock due to Felix' global lock and a
> synchronized block in Felix HTTP WhiteboardManager implementation.
> This issue is about finding a way to fix the issue originally described in
> SLING-8051 without trisking a deadlock.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
