[
https://issues.apache.org/jira/browse/FELIX-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503235#comment-13503235
]
Guillaume Nodet commented on FELIX-3781:
----------------------------------------
I've managed to debug the problem and the happens because in the
ManagedServiceTracker#updateService, the configs local variable is null.
I think it happens because the configuration are put in the tracker map *after*
the call to addingService(), while the thread is scheduled in this call. So
there may be cases where the scheduled thread can be started and the configs
variable retrieved *before* it is actually set, leading to the service not
being called at the end.
> ConfigAdmin issue where the ManagedService is registered, the configuration
> available but the service is not called
> -------------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-3781
> URL: https://issues.apache.org/jira/browse/FELIX-3781
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
> Reporter: Guillaume Nodet
>
> It sometimes happen at Karaf startup.
> I've investigated the problem a bit and by looking at the ConfigAdmin object
> when in such a state, I could find the ManagedService in the tracker and the
> configuration is available in the configuration map.
> The configuration is even bound to the correct bundle.
> Still the service isn't called and I have a log statement the first line of
> the updated() method to check about that.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
