Hi, I think I just found the problem. Stepping into the code, I noticed that this problem occures when Karaf tries to install a bundle and it cannot read the Manifest. Checking again, I noticed that any time I have a failure, this is on a bundle that I unzipped, fixed Manifest and zipped again using a file archiver (7-zip to be precise).
So it seems that a jar is not "just" a zip file, but the Manifest must appear at some place in the archive. When it cannot load the manifest, Karaf throws an exception that ends up finally showing "null" on the command line. To find the responsible bundle: - use features:install -c, the last installed bundle is the faulty one - or activate the "trace" log level and check the logs for the last bundle being installed. Note that this problem occures event if the bundle is already installed, because Karaf checks for version updates. Vincent Pgaz wrote: > > Hi, > > I'm currently experiencing the same problem. > I'm working with Apache Karaf 1.2.0 and I'm unable to find out why this > error is happening. > I think something's wrong in the download/install/start mechanism of the > features module of karaf, because as you said, it perfectlly works when > deploying by hand (I mean install -s ...). > > Any idea about that ? > Does it come from a malformed feature.xml, or a problem in the activator ? > > Thanks, > > > TheWinch wrote: >> >> Hello, >> >> I'm experiencing a strange problem with the "features" functionality of >> Karaf. I'm trying to install a feature (which contains a single bundle), >> but it doesn't install. On the console I see a single debug message >> appear: >> >> ka...@root>features:install camel-activemq >> null >> >> I have installed manually all dependencies of activemq-camel. Then, I >> have tried to make another feature which just contains the activemq-camel >> bundle (v5.3.0) but I get the same result. When I install the bundle in >> isolation (using osgi:install -s) it works perfectly. >> >> Did someone already see this happen ? I have the same problem with a >> bundle of mine. I don't have a single clue about the problem (putting the >> log level to TRACE didn't help either). >> >> Thanks! >> >> Vincent >> > > -- View this message in context: http://old.nabble.com/-SMX4.1--Feature-won%27t-install-but-the-osgi-bundle-installs-fine-tp27270459p27564518.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
