[
https://issues.apache.org/jira/browse/KARAF-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15677654#comment-15677654
]
Guillaume Nodet edited comment on KARAF-4158 at 11/18/16 8:26 PM:
------------------------------------------------------------------
"featureA will never start as featureB never got into STARTED"
This usually means a bad behaving feature. You can use prerequisite="true" to
ensure the dependent feature is started before installing the other one.
Another way to express the same thing is to use staged boot features.
was (Author: gnt):
"featureA will never start as featureB never got into STARTED"
This usually means a bad behaving feature. You can use prerequisite="
> Unexpected behavior on first startup
> ------------------------------------
>
> Key: KARAF-4158
> URL: https://issues.apache.org/jira/browse/KARAF-4158
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
> Affects Versions: 4.0.3
> Environment: RHEL 6.2 x32, Java 1.8.0_72-ea-b05
> Reporter: Jean-Philippe CLEMENT
> Assignee: Christian Schneider
> Fix For: 4.1.0, 4.0.6
>
>
> This problem only occurs on the very first startup of a custom assembly. This
> means unpacking the assembly .tar.gz then run karaf. This issue is not 100%
> reproducible. Several untar/run might be necessary to reproduce the issue.
> The problem comes with Blueprint property-placeholders. User bundles might be
> started and not get .cfg replaced properties but the "$(PARAM_NAME)" itself
> (String property).
> I suspect user bundles to be started before the .cfg files are populated in
> the /etc directory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
