[
https://issues.apache.org/jira/browse/KARAF-6080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16739360#comment-16739360
]
J. Brébec commented on KARAF-6080:
----------------------------------
Thanks !
We have a Managed Service (through DS) which implements the Servlet API, and
are deployed to jetty with pax-exam whiteboad. When this bug occurs, two
servlets with the same alias are registered, which fails. We have a lot of IT
with PaxExam, and 10% of these tests fail because of this bug. In my usecase,
this issue can have a big impact of the availability of my services.
> Duplicate configuration randomly created on the first start in
> ConfigurationAdmin
> ---------------------------------------------------------------------------------
>
> Key: KARAF-6080
> URL: https://issues.apache.org/jira/browse/KARAF-6080
> Project: Karaf
> Issue Type: Bug
> Components: karaf
> Affects Versions: 4.2.2
> Environment: Karaf 4.1.2, Karaf 4.2.2
> Windows 7, Equinox
> Reporter: J. Brébec
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 4.1.8, 4.2.3
>
> Attachments: karaf-6080.patch
>
>
> On the first start, if a boot feature contains a <config/> element, and the
> associated .cfg file exists in the etc folder, then this Configuration can be
> created twice in ConfigurationAdmin :
> # File Install check the etc folder and create for every cfg a Configuration
> in ConfigurationAdmin
> # the FeatureService (FeatureConfigInstaller), when a feature is installed
> and has a configuration, check if this configuration exists in
> ConfigurationAdmin. If the configuration doesn't exists, then it creates a
> new one
> If 1 and 2 are executed simultaneously, then the same configuration is
> created twice in ConfigurationAdmin. If this configuration is linked to a
> managed service, then this service will be instanciated twice.
> By default, the karaf-maven-plugin copies every cfg to the etc folder, this
> issue can probably be triggered by any <config/> element on a boot feature.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
