karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-4158) Unexpected behavior on first startup
Date Mon, 21 Nov 2016 12:23:59 GMT

    [ https://issues.apache.org/jira/browse/KARAF-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683449#comment-15683449

Guillaume Nodet commented on KARAF-4158:

Also, I think it would be interesting to better understand your use case:
Problem gets more worse when we have custom features where featureA depends on featureB, and
if order gets change during startup, featureA will never start as featureB never got into
STARTED state.

You may go the wrong way and it may be easier to fix the problem in a better way, but you
need to explain what the problem is.

> 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

This message was sent by Atlassian JIRA

View raw message