[
https://issues.apache.org/jira/browse/KARAF-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350534#comment-15350534
]
Christian Schneider commented on KARAF-4158:
--------------------------------------------
In OSGi it can not be guaranteed that the configs are available on startup in
config admin. You have to allow reloading of the context in blueprint so the
correct configs can be applied when they are available.
Does this solve the issue?
> 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
> 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)
