[
https://issues.apache.org/jira/browse/SLING-5631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455808#comment-15455808
]
Ivo Leitão commented on SLING-5631:
-----------------------------------
Hi !
After a long period I've finally had time to look at this in greater detail.
Unfortunately this was caused by my environment. I'm using BndTools for
development and there is a property that instructs the running framework
(felix) to do not keep the bundle private area configurations (I don't know why
the default setting is false, that seems a little odd...).
After many debugging sessions in the source code of the sling installer I've
reached the conclusion that the RegisteredSourceLists.ser file was being
deleted in each startup of the environment therefore the duplication that I was
having.
Anyway the solution was to set -runkeep property must be set to true in the
bndtools run configuration. Also I don't know how fileinstall was working
without a similar mechanism to the one used by the sling installer but this
was the problem in my environment.
For anyone with a similar problem this
[link|https://groups.google.com/forum/#!searchin/bndtools-users/launch.keep%7Csort:relevance/bndtools-users/-exa7MbJJ0A/wGzVklIbaDcJ]
from the bndtools ma\iling list gives some insight on the problem
Finally thank for the support and sorry for bringing up something as a bug that
is clearly and environment problem. This issue can be closed
Best Regards
> 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 Core 3.6.8, File Installer 1.1.0, Installer
> Configuration Factory 1.1.2
> Environment: Linux; bndtools;
> Reporter: Ivo Leitão
> Priority: Minor
> Attachments: cpeng.error.05-31-2016.log, log.zip,
> org.apache.sling.commons.log.LogManager.factory.config-debug.log.config,
> org.apache.sling.commons.log.LogManager.factory.writer-debug.log.config
>
>
> 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)
