Hi Benson Don't you have any refresh in test ? Most the time invalid bundle context is caused by a refresh. So the "initial" bundle context is no more valid.
Regards JB On Sep 14, 2016, 20:54, at 20:54, Benson Margulies <[email protected]> wrote: >Folks, > >One of my pax-exam tests _sometimes_ fails with the backtrace below; >to be more precise, it hangs after showing this backtrace on the >console. > >It seems as if this only happens when all of my ITs run; if I tell >failsafe to just run one, it seems never to happen. > >Any ideas? > >TIA > > >2016-09-14 14:46:52,074 | WARN | pool-6-thread-1 | Activator > | 6 - org.apache.karaf.features.core - 4.0.6 | 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:293)[6:org.apache.karaf.features.core:4.0.6] >at >org.apache.karaf.features.internal.osgi.Activator.doStart(Activator.java:265)[6:org.apache.karaf.features.core:4.0.6] >at >org.apache.karaf.util.tracker.BaseActivator.run(BaseActivator.java:236)[6:org.apache.karaf.features.core:4.0.6] >at >java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_60] > at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_60] >at >java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_60] >at >java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_60] > at java.lang.Thread.run(Thread.java:745)[:1.8.0_60]
