[
https://issues.apache.org/jira/browse/KARAF-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Achim Nierbeck reopened KARAF-295:
----------------------------------
This would have been my expectation, but :)
It looks like it "caches" it's old configuration over restart, and adds another
configuration for the one available through the
org.apache.felix.fileinstall-deploy.cfg file.
But this isn't the only service that is affected, all services that are
configurable had this effect.
So with every restart you get a new entry, and actually I think you also have
those services configured and running.
Just one example when I was debugging the pax-war deployer I hit the breakpoint
in 4 different running implementations/services which I think I shouldn't have
:)
> Webconsole - Configuration Admin, shows multiple entries for FileInstall
> after restart
> --------------------------------------------------------------------------------------
>
> Key: KARAF-295
> URL: https://issues.apache.org/jira/browse/KARAF-295
> Project: Karaf
> Issue Type: Bug
> Affects Versions: 2.2.0
> Reporter: Achim Nierbeck
> Assignee: Guillaume Nodet
>
> For each restart of the Karaf, the ConfigurationAdmin Webconsole Plugin shows
> a new entry for the FileInstaller (maybe even for other managed services,
> too).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
