[
https://issues.apache.org/jira/browse/SLING-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger reopened SLING-310:
-------------------------------------
Outsch ! I found the actual problem.... The SlingServletContext which is
registered in the SlingMainServlet.activate() method as an OSGi service is
never unregistered and thus clients may still refer to that server ....
We must make sure in the SlingMainServlet.deactivate() method to dispose off -
and thus unregister - the SlingServletContext ...
> SlingMainServlet still used as the HttpContext after being deactivated
> ----------------------------------------------------------------------
>
> Key: SLING-310
> URL: https://issues.apache.org/jira/browse/SLING-310
> Project: Sling
> Issue Type: Bug
> Reporter: Bertrand Delacretaz
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
> Attachments: log.txt, SLING-310-0954.patch, SLING-310-debug.log,
> SLING-310-fmeschbe.patch, SLING-310.log
>
>
> In revision 633868, with this build/start sequence:
> cd launchpad/webapp
> cd ../app ; mvn clean install ; cd - ; mvn clean integration-test
> -Dintegration.test.wait=true
> Some integration tests fail, like for example
> PropertyRenderingTest.testTextNoExt
> The problem is that mimeTypeService is null here:
> HttpContext httpContext = new HttpContext() {
> public String getMimeType(String name) {
> return mimeTypeService.getMimeType(name);
> }
> event though the mimeTypeService of the enclosing class is set.
> Not sure what's happening, maybe there are several instances of this
> HttpContext around.
> To simplify, I'll change SlingMainServlet to implement HttpContext
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
