Hi, I've been developing a large ESB project using Karaf 2.1.3. I have a number of bundles that I've started hot-deploying by dropping feature repositories/descriptors in the deploy directory. I've observed some odd behavior since I've started doing this whenever Karaf is restarted.
First of all, if the xml files containing the features are left in the deploy directory, every time Karaf is restarted a duplicate feature with the same name and version is added to the features list for every feature in the xmls. So after five restarts I'll see five copies of the same features in the list. This is not true of the bundles contained within the features, however. There is still only one instance of each bundle in the bundle list. The main problem with this, besides the fact that the features list becomes a bit polluted, is that after this happens I have had spotty success when attempting to uninstall features by deleting the xml files. Sometimes it works, sometimes it may only uninstall one instance of the features and the bundles continue running. Secondly I have noticed that if I delete any previously deployed features xmls from the deploy directory while Karaf is off, they are not being uninstalled when it is started it up again. Basically, the only stable way I've been able to hot-deploy features is to either never turn Karaf off or, if I have to shut it down, I must do a full reset by deleting the data directory before I start it up again. I'm not sure if this no longer happens in Karaf 2.2 as I'm using ServiceMix 4.3, which is locked into using Karaf 2.1.3. -- View this message in context: http://karaf.922171.n3.nabble.com/Features-deployer-unexpected-behavior-tp3106858p3106858.html Sent from the Karaf - User mailing list archive at Nabble.com.
