In the case you mention karaf is not completely rebooting. It just restarts the shell and the ssh server. This happens if some optional dependency of the shell changes. Can you try feature:install -v and post the output? It should report what bundles are refreshed and why.
Christian 2016-01-07 16:55 GMT+01:00 Daniel McGreal <[email protected]>: > Hi Karaf users! (Though I think this one is likely for JB…) > > I have a reasonably complex application in 4.0.3 which, upon > feature:install, causes a reinitialisation of Karaf. It’s only reasonably > been the case, but when I run a command like: > > feature:install a b c d e f > > via bin/karaf’s console, when the command returns, I get a reprint of the > welcome screen. If I execute it via ssh then my SSH connection is dropped > and I have to wait till I can reconnect. > > Further commands like feature:install, uninstall, etc give me an NPE: > > 2016-01-07 15:52:40,256 | ERROR | nsole user karaf | ShellUtil > | 44 - org.apache.karaf.shell.core - 4.0.3 | Exception caught > while executing command > java.lang.NullPointerException > at > org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:220)[9:org.apache.karaf.features.core:4.0.3] > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:263)[9:org.apache.karaf.features.core:4.0.3] > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1079)[9:org.apache.karaf.features.core:4.0.3] > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:975)[9:org.apache.karaf.features.core:4.0.3] > at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_65] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_65] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_65] > at java.lang.Thread.run(Thread.java:745)[:1.8.0_65] > > > I haven’t attached the logging, because there’s lots of it. Nothing > immediately stands out - there aren’t any exceptions or logging before the > usual startup logging (talking about locks). > > Very best, Dan. > -- -- Christian Schneider http://www.liquid-reality.de <https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7e46&URL=http%3a%2f%2fwww.liquid-reality.de> Open Source Architect http://www.talend.com <https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7e46&URL=http%3a%2f%2fwww.talend.com>
