Description
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.
Attachments
Attachments
Issue Links
- is superceded by
-
KARAF-4723 Karaf sometimes will prioritize bundles in deploy folder at first start regardless of run level
- Resolved
- relates to
-
KARAF-4578 Fileinstaller does not install bundle to root region after clean start
- Resolved