[
https://issues.apache.org/jira/browse/KARAF-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106381#comment-15106381
]
Jean-Baptiste Onofré commented on KARAF-2522:
---------------------------------------------
OK, the problem is that:
{code}
} else {
System.out.println("NO CLASS IF FAILURE");
// Force start of bundles so that they are flagged as
persistently started
for (Bundle b : state.installed) {
try {
b.start();
} catch (Exception e2) {
// Ignore
}
}
}
{code}
the bundle is started whatever the start flag is. I'm fixing that.
> Boot feature bundle failure forces other bundles to start regardless 'start'
> flag
> ---------------------------------------------------------------------------------
>
> Key: KARAF-2522
> URL: https://issues.apache.org/jira/browse/KARAF-2522
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
> Affects Versions: 2.3.2, 2.3.3
> Reporter: Alexey Gavrilov
> Assignee: Jean-Baptiste Onofré
> Fix For: 2.3.12, 2.4.4, 3.0.6
>
>
> If a bundle under a boot feature fails to start, then all the bundles marked
> as 'start="false"' will be forced to start during handling an error.
> Steps to reproduce:
> - create a boot feature containing two bundles.
> - make the first bundle fail on startup (due to missing dependency, for
> example)
> - mark the second bundle as 'start=false'
> - start the Karaf container
> - the first bundle will fail to start
> - the second bundle will be started regardless the 'start=false' flag.
> I think the problem is around the start bundle loop at
> FeaturesServiceImpl.java:525 (in Karaf 2.3.2) which doesn't respect the
> bunlde startup flag when starting the installed bundles when
> 'Option.NoCleanIfFailure' is set.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
