Here is a snippet from the log that might be relevant
2016-09-08 21:52:42,941 | INFO | ool-188-thread-1 | FeaturesServiceImpl
| 11 - org.apache.karaf.features.core - 4.0.5 | Changes to perform:
2016-09-08 21:52:42,945 | INFO | ool-188-thread-1 | FeaturesServiceImpl
| 11 - org.apache.karaf.features.core - 4.0.5 | Region: root
2016-09-08 21:52:42,945 | INFO | ool-188-thread-1 | FeaturesServiceImpl
| 11 - org.apache.karaf.features.core - 4.0.5 | Bundles to install:
2016-09-08 21:52:42,945 | INFO | ool-188-thread-1 | FeaturesServiceImpl
| 11 - org.apache.karaf.features.core - 4.0.5 |
mvn:com.example.auth/pki-data/2.0.1.SNAPSHOT
2016-09-08 21:52:42,945 | INFO | ool-188-thread-1 | FeaturesServiceImpl
| 11 - org.apache.karaf.features.core - 4.0.5 |
mvn:com.example.auth/pki-data-h2/2.0.1.SNAPSHOT
2016-09-08 21:52:42,946 | INFO | ool-188-thread-1 | FeaturesServiceImpl
| 11 - org.apache.karaf.features.core - 4.0.5 |
mvn:org.osgi/org.osgi.service.jdbc/1.0.0
2016-09-08 21:52:42,946 | INFO | ool-188-thread-1 | FeaturesServiceImpl
| 11 - org.apache.karaf.features.core - 4.0.5 | Stopping bundles:
2016-09-08 21:52:42,950 | INFO | ool-188-thread-1 | FeaturesServiceImpl
| 11 - org.apache.karaf.features.core - 4.0.5 |
org.apache.karaf.features.core/4.0.5
2016-09-08 21:52:42,970 | INFO | ool-188-thread-1 | CommandExtension
| 138 - org.apache.karaf.shell.core - 4.0.5 | Unregistering commands for
bundle org.apache.karaf.features.command/4.0.5
2016-09-08 21:52:43,032 | WARN | ool-177-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-08 21:52:43,049 | INFO | ool-236-thread-2 | CommandExtension
| 138 - org.apache.karaf.shell.core - 4.0.5 | Unregistering commands for
bundle org.apache.karaf.kar.core/4.0.5
Afterward there are no more messages from FeaturesServiceImpl and the bundle
is left in the resolved state. If I manually start the bundle I see the
Karaf branding page again and all the features load properly. Is this a
feature installer bug? How can I troubleshoot this?
--
View this message in context:
http://karaf.922171.n3.nabble.com/Inconsisent-behavior-during-Karaf-4-0-5-startup-tp4047933p4047934.html
Sent from the Karaf - User mailing list archive at Nabble.com.
