[
https://issues.apache.org/jira/browse/KARAF-4498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volker Althaus updated KARAF-4498:
----------------------------------
Attachment: bug-screencast.mp4
Screencast which shows the setup and two clean Karaf starts. The first one
works and the CamelContext is there, the second one fails and the context list
remains empty.
> 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 correctly.
> 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
(v6.3.4#6332)
