You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Julian Sedding (JIRA)" <ji...@apache.org> on 2018/12/20 13:05:00 UTC

[jira] [Created] (SLING-8187) Deadlock in SlingMainServlet after SLING-8051

Julian Sedding created SLING-8187:
-------------------------------------

             Summary: 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


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)