Hi Florin, Besides the questions of JB, were you able to reproduce the same behavior with equinox as framework? Cause from this description plus your question at stackoverflow, it gives me the impression that the cache does get corrupted. Since Karaf uses a newer version of Felix it might be a recession of Felix.
Regards, Achim sent from mobile device Am 20.01.2014 18:44 schrieb "Jean-Baptiste Onofré" <[email protected]>: > Hi Florin, > > 1/ regarding webconsole, it's because you have to install the plugins. > If you take a look in the Karaf standard feature, you will see that you > have a condition when installing the webconsole: the other webconsole > plugins are installed (instance, features, gogo, http, scr, ...). > So, when you install as a boot feature, you have to go through the > condition. Try to put the webconsole at the end of the boot features set > with in sync mode. > > 2/ regarding bundle, do you reproduce the issue if you: > 2.1/ install a bundle (with bundle:install) > 2.2/ restart Karaf > I'm pretty sure you don't have issue here. > Do you use OBR with ACE ? What's your ACE version ? > By the way, did you evaluate other provisioning solution (Fabric, Cellar, > Kalumet, ...) ? > > Thanks > Regards > JB > > On 01/20/2014 06:16 PM, F.Aubele wrote: > >> Hi everyone, >> I have 2 major problems right now. I'm using the official karaf 3 release >> and felix as container implementation. Karaf is running on linux. >> The first problem i have is that i want to install certain features as >> boot >> features. >> These features are: >> webconsole,eventadmin,blueprintweb,jndi,obr. >> >> If i put these features into the featuresBoot list in >> org.apache.karaf.features.cfg, the web console is only showing the OSGI >> and >> WebConsole Tab, the Main tab and the event entry in the osgi tab are >> missing. After feature:uninstall and feature:install in the shell, >> everything works fine again. >> >> The second problem is much more problematic for me right now: >> If i do a forced shutdown of the VM I run Karaf on, all bundles i have >> installed via the WebConsole won't start up again. This happens when i run >> karaf as a service and when i start it manually. At first i thought it had >> something to do with blueprint, since most of my bundles are using it, but >> it also happens with the apache ace managementagent bundle. >> >> Most of the time the error looks like this: >> >> Unresolved constraint in bundle org.apache.ace.managementagent [166]: >> Unable >> to resolve 166.0: missing requirement [166.0] osgi.wiring.package; >> (&(osgi.wiring.package=org.osgi.service.deploymentadmin)( >> managementagent=true)(version>=1.0.0)(!(version>=2.0.0))). >> >> I get this error,too: >> >> ERROR: Error reloading cached bundle, removing it: >> /srv/apache-karaf-3.0.0/data/cache/bundle165 >> (java.lang.NullPointerException) >> >> which maybe leads to the missing requirements, but i did not get the NPE >> for >> every installed bundle. >> >> After restarting, the installed bundles are still in the cache-folder, but >> are not visible in the bundle list of the web-console or via the list >> command in the shell. In the log files every manually installed bundle is >> missing some requirements or is removed because of "Error reloading cached >> bundle". >> If i delete the bundles from the cache folder, restart the karaf >> service/server and install the bundles manually again, everything works >> fine. If i do not remove the bundles from the cache folder, it is not >> possible to install the bundles again manually, error message is: >> >> Cannot install or update bundle from >> /srv/apache-karaf-3.0.0/data/tmp/install116617036763718115.tmp >> org.osgi.framework.BundleException: Bundle installation rejected by hook. >> >> It seems that this does not happen with installed features, but only with >> manually deployed bundles. It's really sad, because I like Karaf 3 a lot >> more than geronimo, but i need a working restart in case of power loss. >> >> I will try to create more detailed stack traces. >> Workaround could be to: >> a)deploy the bundles into the system repository, so they will be seperated >> from the data folder/cache (this was working when using geronimo) or >> b)create a feature out of my bundles and add this feature to the boot >> features. >> Since I want to use Apache Ace for bundle provisioning, I'm not sure how >> these workarounds will work out long term. >> I have the feeling that using the bundle cache would greatly simplify >> things >> in this regard. >> Every help is appreciated. >> Thanks >> F.Aubele >> >> >> >> >> >> >> >> -- >> View this message in context: http://karaf.922171.n3.nabble. >> com/Problems-with-webconsole-and-bundle-cache-tp4031218.html >> Sent from the Karaf - User mailing list archive at Nabble.com. >> >> > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com >
