[SLING-8187] Deadlock in SlingMainServlet after SLING-8051

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Engine 2.6.16
• Fix Version/s: Engine 2.6.18
• Component/s: Engine
• Assignee: Julian Sedding
• Reporter: Julian Sedding
• Created: 20/Dec/18 13:04
• Updated: 11/Jan/19 16:11
• Resolved: 07/Jan/19 12:40

Description

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.

Issue Links

• is caused by: SLING-8051 Timing issue in SlingMainServlet
• links to: GitHub Pull Request #6