[
https://issues.apache.org/jira/browse/KARAF-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683107#comment-15683107
]
Christian Schneider edited comment on KARAF-4158 at 11/21/16 10:18 AM:
-----------------------------------------------------------------------
Can you provide the pom how you create the custom distro in a github repo. I
can then try to reproduce as well as provide a working way.
If it only happens with your own custom code then I doubt we can help you here
or on the karaf user list. In that case you can try to get support from any
of the commercial support offerings:
http://karaf.apache.org/community.html#support
was (Author: ch...@die-schneider.net):
Can you provide the pom how you create the custom distro in a github repo. I
can then try to reproduce as well as provide a working way.
If it only happens with your own custom code then I doubt we can help you here
or on the karaf user list. In that case you can try to get support from any
of the commercial support offerings:
> 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
>
>
> 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)
