[
https://issues.apache.org/jira/browse/SLING-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576943#action_12576943
]
Felix Meschberger commented on SLING-310:
-----------------------------------------
I modified the Apache Felix Configuration Admin implementation a bit and this
seems to work and re-reading the logs provided by Carsten now show exactly,
that we were on the right track regarding what was going:
Thread T2 was registering a ManagedServiceFactory
In T2 the ConfigurationAdmin service sees the service and schedules
configuration of it
Thread T1 was creating and setting a configuration C
In T1 the ConfigurationAdmin service schedules the update of the
ManagedServiceFactory
Thread T3 handles the first scheduled task of initially providing the
service with configuration
(created by T2 in the meantime)
Thread T3 handles the second scheduled task of updating the configuration
Hence the ManagedServiceFactory is updated twice with the same configuration
and thus cycles the service.
The provisional fix is to record in the Configuration object that it was sent
to the consuming service and to prevent sending the update of a configuration,
which has already been sent.
See also FELIX-516
> 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
> 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.
