jsedding opened a new pull request #6: SLING-8187 - Deadlock in SlingMainServlet after SLING-8051 URL: https://github.com/apache/sling-org-apache-sling-engine/pull/6 - register SlingServletContext asynchronously - make SlingServletContext#dispose a no-op on subsequent calls This solution has the following drawback: - SlingServletResolver has a mandatory reference to SlingServletContext, thus deferring registration of SlingServletContext causes registration of SlingServletResolver - SlingRequestProcessor (via SlingMainServlet) has a dynamic optional reference to SlingServletResolver, but throws an exception causing a 503 response while no SlingServletResolver is bound --> thus the time-window for this 503 response increases with this fix - with the fix applied, I see it frequently if there are requests to my system during startup; without the fix I could not observe any.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
