Ivo Leitão created SLING-5631:
---------------------------------
Summary: File Installer generating new pid's for factory in each
start of the framework
Key: SLING-5631
URL: https://issues.apache.org/jira/browse/SLING-5631
Project: Sling
Issue Type: Bug
Components: Installer
Affects Versions: Installer Configuration Factory 1.1.2, File Installer
1.1.0, Installer Core 3.6.8
Environment: Linux; bndtools;
Reporter: Ivo Leitão
Hi,
I'm changing from felix file installer to Sling file installer and I stumbled
upon a problem that I was not seeing on felix file installer. I'm using
bndtools to develop and I make multiple restarts. The first time I booted the
felix framework I dint't have any problems. The second time my factory
configurations became repeated. To give an example:
First Boot:
05e9adef-c7a9-49b5-a243-39f029e4389c.config
factory.config with:
factory.pidList=[ \
"platform.directory.datasource.05e9adef-c7a9-49b5-a243-39f029e4389c", \
]
Second Boot:
05e9adef-c7a9-49b5-a243-39f029e4389c.config
5b18e3a2-6bc3-497e-9b3c-e09107552df8.config
factory.config with:
factory.pid="platform.directory.datasource"
factory.pidList=[ \
"platform.directory.datasource.5b18e3a2-6bc3-497e-9b3c-e09107552df8", \
"platform.directory.datasource.05e9adef-c7a9-49b5-a243-39f029e4389c", \
]
This was not happening with file install. Is this by design and I need to clean
config admin dir's every time I boot or a bug in file install ?
This is causing multiple problems inclusive with sling log component wich
immediately complains with and exception
30.03.2016 19:14:37.697 *ERROR* [CM Configuration Updater (Update:
pid=org.apache.sling.commons.log.LogManager.factory.config.30a7d154-cf89-47da-a1af-62afd3c6f96d)]
org.apache.felix.configadmin.1.8.8
[[org.osgi.service.cm.ConfigurationAdmin]][org.osgi.service.cm.ManagedServiceFactory,
id=7
Updating property org.apache.sling.commons.log.names of configuration
org.apache.sling.commons.log.LogManager.factory.config.30a7d154-cf89-47da-a1af-62afd3c6f96d
caused a problem: Category platform already defined by configuration
org.apache.sling.commons.log.LogManager.factory.config.30a7d154-cf89-47da-a1af-62afd3c6f96d
org.osgi.service.cm.ConfigurationException: org.apache.sling.commons.log.names
: Category platform already defined by configuration
org.apache.sling.commons.log.LogManager.factory.config.30a7d154-cf89-47da-a1af-62afd3c6f96d
at
org.apache.sling.commons.log.logback.internal.config.LoggerManagedServiceFactory.updated(LoggerManagedServiceFactory.java:36)
at
org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.updated(ManagedServiceFactoryTracker.java:159)
at
org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.provideConfiguration(ManagedServiceFactoryTracker.java:93)
at
org.apache.felix.cm.impl.ConfigurationManager$UpdateConfiguration.run(ConfigurationManager.java:1753)
at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:143)
at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:110)
at java.lang.Thread.run(Thread.java:745)
Caused by:
org.apache.sling.commons.log.logback.internal.config.ConfigurationException:
at
org.apache.sling.commons.log.logback.internal.LogConfigManager.updateLoggerConfiguration(LogConfigManager.java:533)
at
org.apache.sling.commons.log.logback.internal.config.LoggerManagedServiceFactory.updated(LoggerManagedServiceFactory.java:34)
... 6 common frames omitted
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
