I've already submitted a post on this here
<http://karaf.922171.n3.nabble.com/Inconsisent-behavior-during-Karaf-4-0-5-startup-td4047933.html#a4047934>
. Basically the Apache Karaf Features Core bundle get stuck in a "Resolved"
state.
karaf@root>la | grep -i feature
11 | Resolved | 15 | 4.0.5 | Apache Karaf :: Features :: Core
136 | Active | 26 | 4.0.5 | Apache Karaf :: Deployer ::
Features
141 | Active | 30 | 4.0.5 | Apache Karaf :: Features ::
Command
I have to manually start the bundle in order for remaining features to
continue loading properly. The last log entries that relate to
FeaturesServiceImpl are here:
2016-09-11 14:44:36,195 | INFO | pool-49-thread-1 | FeaturesServiceImpl
| 11 - org.apache.karaf.features.core - 4.0.5 | Stopping bundles:
2016-09-11 14:44:36,195 | INFO | pool-49-thread-1 | FeaturesServiceImpl
| 11 - org.apache.karaf.features.core - 4.0.5 |
org.apache.sshd.core/0.14.0
2016-09-11 14:44:36,227 | INFO | pool-49-thread-1 | FeaturesServiceImpl
| 11 - org.apache.karaf.features.core - 4.0.5 |
org.apache.karaf.features.core/4.0.5
2016-09-11 14:44:36,299 | INFO | pool-49-thread-1 | CommandExtension
| 155 - org.apache.karaf.shell.core - 4.0.5 | Unregistering commands for
bundle
org.apache.karaf.features.command/4.0.5
2016-09-11 14:44:36,363 | INFO | ool-106-thread-2 | CommandExtension
| 155 - org.apache.karaf.shell.core - 4.0.5 | Unregistering commands for
bundle
org.apache.karaf.kar.core/4.0.5
2016-09-11 14:44:36,374 | INFO | ool-145-thread-1 | JettyFactoryImpl
| 220 - org.ops4j.pax.web.pax-web-jetty - 4.2.6 | SPDY not available,
creating
standard ServerConnector for Http
2016-09-11 14:44:36,375 | WARN | pool-38-thread-1 | Activator
| 11 - org.apache.karaf.features.core - 4.0.5 | Error starting activator
java.lang.IllegalStateException: Invalid BundleContext.
at
org.apache.felix.framework.BundleContextImpl.checkValidity(BundleContextImpl.java:511)[org.apache.felix.framework-5.4.0.jar:]
at
org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:328)[org.apache.felix.framework-5.4.0.jar:]
at
org.apache.karaf.util.tracker.BaseActivator.registerMBean(BaseActivator.java:290)[11:org.apache.karaf.features.core:4.0.5]
at
org.apache.karaf.features.internal.osgi.Activator.doStart(Activator.java:264)[11:org.apache.karaf.features.core:4.0.5]
at
org.apache.karaf.util.tracker.BaseActivator.run(BaseActivator.java:233)[11:org.apache.karaf.features.core:4.0.5]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_91]
at
java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_91]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_91]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_91]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_91]
2016-09-11 14:44:36,401 | INFO | ool-145-thread-1 | JettyServerImpl
| 220 - org.ops4j.pax.web.pax-web-jetty - 4.2.6 | Pax Web available at
Any thoughts on what might cause this or how to troubleshoot?
[0.0.0.0]:[8181]
--
View this message in context:
http://karaf.922171.n3.nabble.com/Features-Core-bundle-stuck-in-Resolved-state-tp4047964.html
Sent from the Karaf - User mailing list archive at Nabble.com.
