karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Graf (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-4498) Fileinstall polls too early on clean start
Date Sun, 19 Jun 2016 05:40:05 GMT

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

Benjamin Graf commented on KARAF-4498:

Hi Volker,

could you have a look on if your bundle got's successfully installed. You may also look into
digraph.json under data\cache\bundle<xxx>\data (bundleid of mvn:org.apache.karaf.features/org.apache.karaf.features.core/4.0.5).
Maybe the reason is the same as in KARAF-4578.


> Fileinstall polls too early on clean start
> ------------------------------------------
>                 Key: KARAF-4498
>                 URL: https://issues.apache.org/jira/browse/KARAF-4498
>             Project: Karaf
>          Issue Type: Bug
>    Affects Versions: 4.0.4
>         Environment: Windows 7
>            Reporter: Volker Althaus
>         Attachments: bug-screencast.mp4, bug-setup.zip
> In the deploy folder is a bundle with a Spring driven Camel route. As boot features "camel-spring"
and "spring-dm" are given.
> On a clean Karaf start in nearly 9 out of 10 times the CamelContext is started, but the
"context-list" command output is empty, the Camel route itself however is started and running
> Is looks like fileinstall does not regard the property "felix.fileinstall.active.level=80"
and polls too early, so likely some BundleListeners like the one which registers the CamelContext
for the "context-list" command are not available yet.
> A real hot deploy at runtime works all time, the context appears correctly.
> In Karaf 2 and 3 this issue did not appear.
> Attached to this issue is a setup with the hot deploy folder and a customized features.cfg.
Simple extract into a vanilla Karaf 4.0.4. Because it is a timing problem and it could be
not reproducible, on demand I can also attach a screencast which shows the bug on my system.

This message was sent by Atlassian JIRA

View raw message