FWIW, for the upcoming pax-exam 4.10, we offer a chance to rerun the test if
the testcase implements a retry TestRule, so that when the test failed first
time with such bundle refresh problem, there’s another chance to rerun it with
a refreshed Karaf container. PAXEXAM-795[1] tracked this.
Such an error is caused by the bundle being stopped / refreshed / updated,
so the reason should appear in the log.
2016-09-14 21:10 GMT+02:00 Benson Margulies :
> I don't know of any reason for a refresh. The structure is always that
> I have a Karaf assembly; the test
I don't know of any reason for a refresh. The structure is always that
I have a Karaf assembly; the test launches it and then tests web
services that it publishes. No test involves any updating or deploying
features or bundles.
On Wed, Sep 14, 2016 at 2:59 PM, Guillaume Nodet
If your test deploys certain bundles such as eventadmin, it can cause
pax-logging-api to be refreshed, which in turn cause almost all bundles to
be refreshed, which can cause such problems.
If that's the case, you should consider deploying eventamin at the startup
stage somehow to avoid the
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 wrote:
>Folks,
>
>One of my pax-exam tests