-
Notifications
You must be signed in to change notification settings - Fork 314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ConfigurationServiceImpl creates duplicate instances #1016
Comments
@ctron it might be temporarily fixed by checking the Equinox clean start property and avoiding updating the configurations read from the snapshot 0. For some historical reasons (corruption of the OSGi storage are) at Eurotech, clean start has always been the choice for embedded systems. |
I've decided to give this a try [1]. To experiment with this branch, the I've noticed a weird behavior in the emulator. Some components are weirdly activated, updated or deactivated (concurrently?) at a very early stage:
I've not yet understood how to get the Felix SCR logs... [1] https://github.com/cdealti/kura/tree/configuration-area-persisted |
Worked a little bit more on this and came up with this branch: https://github.com/eclipse/kura/tree/configService_osgi-clean-false |
This issue is stale because it has been open for 60 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
On startup the Kura ConfigurationServiceImpl does re-create all factory configurations. This results in duplicate service instances. Adding one more for each start.
The reason why this does not manifest into a problem is that Kura forces Equinox to clear the configuration area when starting up.
However this makes the OSGi ConfigAdmin effectively non-persistent and doesn't allow any non-Kura configuration to be stored. It also does not work on Karaf.
The text was updated successfully, but these errors were encountered: