[
https://issues.apache.org/jira/browse/KARAF-4498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15339100#comment-15339100
]
Volker Althaus commented on KARAF-4498:
---------------------------------------
My bundle (58) seems to be installed correctly:
56 | Active | 30 | 1.0.0.6 | Apache ServiceMix :: Bundles ::
aopalliance
57 | Active | 30 | 3.2.0.1 | Apache ServiceMix :: Bundles :: cglib
58 | Active | 80 | 1.0.0 | bug-use-case
59 | Active | 10 | 2.2.6.1 | Apache ServiceMix :: Bundles ::
jaxb-impl
60 | Active | 30 | 0.3.11.1 | Apache ServiceMix :: Bundles ::
not-yet-commons-ssl
The diagraph.json of
mvn:org.apache.karaf.features/org.apache.karaf.features.core/4.0.4:
{"regions":{"root":[0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71,72,73,74,75,76]},"edges":[]}
> 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)
