[
https://issues.apache.org/jira/browse/KARAF-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15676650#comment-15676650
]
Jean-Philippe CLEMENT edited comment on KARAF-4158 at 11/18/16 12:54 PM:
-------------------------------------------------------------------------
We still experience this issue. Is there a workaround such as setting a
higher/lower start level on some bundles.
This issue only occurs during the very first Karaf startup and never happens on
subsequent startups. As mentioned above we are building our custom Karaf
assembly with our features added as "bootFeatures".
was (Author: jeanphi):
We still experience this issue. Is there a workaround such as setting a
higher/lower start level on some bundles.
This issue only occurs during the very first Karaf startup and never happens on
subsequent startups.
> 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)
