[
https://issues.apache.org/jira/browse/KARAF-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15093550#comment-15093550
]
Ralf Steppacher commented on KARAF-4261:
----------------------------------------
I tried on a second machine (3 start/stop cycles). It appears that the
start/stop order is the same per Karaf instance, if that is at all possible
with {{karaf.clean.all = true}}. On the second machine the data access bundle
is consistently started last (3 of 3 times) but is shut as the second bundle
after the _PEP_ bundle (3 of 3 times).
> Bundle start-level seems to be ignored at Karaf restart
> -------------------------------------------------------
>
> Key: KARAF-4261
> URL: https://issues.apache.org/jira/browse/KARAF-4261
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
> Affects Versions: 4.0.3
> Reporter: Ralf Steppacher
>
> AS a workaround for CAMEL-9483 I have set a start-level for my bundles
> deployed as part of my features. This works as expected during initial
> deployment (order of deployment is according to the start levels I set), but
> not during sub-sequent starts of Karaf. It appears the start-level of the
> bundles is ignored, meaning the order of deployment of my bundles is more or
> less random and I observe the issues described in CAMEL-9483 again.
> {{bundle:list}} shows my bundles with the start-levels they have been
> originally deployed with, though.
> As a workaround I set {{karaf.clean.all = true}} in system.properties.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
