Hi,
I have more information about the problem.
The method "start" of the class "org.apache.camel.impl.osgi.Activator"
terminates immediately, after registering a callback ("BundleTracker") to be
notified when the bundle enters the "Active" state in the OSGi point of
view.
However, the Camel initialization is not finished yet, it is performed in
the "addingBundle" method, which registers Camel components, languages, type
converters, ...
It explains the cause of the race condition.
Remark : my application bundle is configured at start-level 60 and all Camel
bundles are configured at start-level 50, therefore it shows that the fix
below might reduce the window of race condition, but will not guarantee that
it does not happen anymore :
https://issues.apache.org/jira/browse/SMX4-744
Should I create a bug in JIRA ?
Regards,
metatech
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-under-OSGi-without-Spring-et-al-tp4507473p5041913.html
Sent from the Camel - Users mailing list archive at Nabble.com.
