The issue comes from Spring-DM which has a big flaw in the sense it can not provide any way to handle those dependencies. We had the same problem and the best way to solve those is to use Aries Blueprint and Camel Blueprint support instead of spring. You could try playing with the bundle start level, but I won't solve all the problems as spring does some things asynchronously wrt the bundles starting, so you'll still have race conditions. It might help a bit though, so feel free to give it a try. I think the easiest way would be to configure fileinstall so that the bundles deployed have a bundle start level greater than the default bundle start level. I can't lookup the exact mechanism right now, but will try this evening if no one gave it to you (I think Charles has experimented things like that IIRC).
On Mon, Aug 16, 2010 at 06:21, Thiago Souza <tcostaso...@gmail.com> wrote: > > Hello there, > > I've setup a production server based on karaf and camel. I've > installed camel through the features mechanism and deployed several spring > xml files that defines components and camel contexts instantiation. > > Everything is fine until the server is restarted. In this case I get > all sort of random problem like type converters that can not be found, > routes based on quartz throwing exceptions and other weird behavior. The > only way to solve this problem is to undeploy all the xml files, restart the > system and redeploy them in a controlled way. > > How can I solve this? Is there any way to start the xmls AFTER all > the camel bundles and have them started in an ordered way? > > Regards, > Thiago Souza > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Karaf-Camel-and-startup-race-conditons-tp1165020p1165020.html > Sent from the Karaf - User mailing list archive at Nabble.com. > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
