Hi,

is your test failing because an @Inject of your service fails?
I think you can add a timeout to the @Inject, in case you have a rather big
setup where the service does take a bit longer to be available after start.

regards, Achim

2017-08-24 10:51 GMT+02:00 Martin Lichtin <[email protected]>:

> Sometimes, not always, a Pax test fails with
>
> org.ops4j.pax.swissbox.tracker.ServiceLookupException: gave up waiting
> for service org.ops4j.pax.exam.ProbeInvokerFactory
>     at org.ops4j.pax.swissbox.tracker.ServiceLookup.
> getService(ServiceLookup.java:161)[304:org.ops4j.pax.
> swissbox.tracker:1.8.2]
>     at org.ops4j.pax.swissbox.tracker.ServiceLookup.
> getService(ServiceLookup.java:104)[304:org.ops4j.pax.
> swissbox.tracker:1.8.2]
>     at org.ops4j.pax.swissbox.tracker.ServiceLookup.
> getService(ServiceLookup.java:87)[304:org.ops4j.pax.
> swissbox.tracker:1.8.2]
>     at org.ops4j.pax.exam.raw.extender.intern.Parser.
> createInvoker(Parser.java:79)[296:org.ops4j.pax.exam.
> extender.service:4.11.0]
>     at org.ops4j.pax.exam.raw.extender.intern.Parser.make(
> Parser.java:68)[296:org.ops4j.pax.exam.extender.service:4.11.0]
>     at org.ops4j.pax.exam.raw.extender.intern.Parser.<init>(
> Parser.java:54)[296:org.ops4j.pax.exam.extender.service:4.11.0]
>     at org.ops4j.pax.exam.raw.extender.intern.TestBundleObserver.
> addingEntries(TestBundleObserver.java:69)[296:org.ops4j.pax.exam.
> extender.service:4.11.0]
>     at org.ops4j.pax.swissbox.extender.BundleWatcher$3.run(
> BundleWatcher.java:226)[301:org.ops4j.pax.swissbox.extender:1.8.2]
>     at java.util.concurrent.Executors$RunnableAdapter.
> call(Executors.java:511)[:1.8.0_141]
>     at java.util.concurrent.FutureTask.run(FutureTask.
> java:266)[:1.8.0_141]
>     at java.util.concurrent.ScheduledThreadPoolExecutor$
> ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.
> java:180)[:1.8.0_141]
>     at java.util.concurrent.ScheduledThreadPoolExecutor$
> ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_141]
>     at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1149)[:1.8.0_141]
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:624)[:1.8.0_141]
>     at java.lang.Thread.run(Thread.java:748)[:1.8.0_141]
>
> Any ideas what could be wrong? In case it is a timing issue, which timeout
> parameter would that be?
>
> - Martin
>
> --
> --
> ------------------
> OPS4J - http://www.ops4j.org - [email protected]
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OPS4J" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>

Software Architect / Project Manager / Scrum Master

-- 
-- 
------------------
OPS4J - http://www.ops4j.org - [email protected]

--- 
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to