I reproduced the problem. Here's what happen: * the feature deployer receives an event about the bundle corresponding to the feature xml in the deploy folder being resolved * it loads the repository and calls FeaturesService#installFeatures with a set bundles flagged with install="auto", in our case, an empty set * the resolver kicks in and find that the wiring of the bundles is wrong and starts to refresh a few bundles * for a still unknown reason, the system bundle is being considered for refresh by felix and causes a reboot
Please raise JIRA issue with the steps to reproduce. I'm not sure where the real bug is though... 2016-11-18 13:35 GMT+01:00 cniehues <christian.nieh...@its-telco.de>: > Ok that seems to work. I can also see that it has 1 bundle less in > comparison > to the deploy folder approach but I can't see which one. > > But I wonder you don't have the restart issue when using the deploy folder. > I've done the following: > * unzip the karaf 4.0.7 distribution > * copied the feature descriptor into deploy folder (already used your > small modification) > * start karaf > * feature:install osgi-test > * shutdown karaf > * start karaf > > And after some seconds it should start to prompt out the startup message > again. > > > > -- > View this message in context: http://karaf.922171.n3.nabble. > com/Installing-drools-module-causing-infinite-karaf- > restart-tp4048644p4048661.html > Sent from the Karaf - User mailing list archive at Nabble.com. > -- ------------------------ Guillaume Nodet ------------------------ Red Hat, Open Source Integration Email: gno...@redhat.com Web: http://fusesource.com Blog: http://gnodet.blogspot.com/
