I double checked and there are no problems on 5.x .. (The issue where that the remote karaf had not registered the ops4j snapshot repo.. After fixing this it works fine)
Thanks On Tue, Feb 20, 2018 at 1:16 PM, nino martinez wael < [email protected]> wrote: > Seems I am hit by this too, at 4.0.11 and are getting a variant on > 5.0.0.M2-SNAPSHOT .. Mine seems to be consistent though.. > > Test: > > https://paste.ofcode.org/msDSMdd8g2nx3ZnfbvWFUG > > Log: > > > dk.netdesign.osgidialer.integrationtest.BackendIntegrationTest, > basicServiceCheck > SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". > SLF4J: Defaulting to no-operation (NOP) logger implementation > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further > details. > Listening for transport dt_socket at address: 5050 > __ __ ____ > / //_/____ __________ _/ __/ > / ,< / __ `/ ___/ __ `/ /_ > / /| |/ /_/ / / / /_/ / __/ > /_/ |_|\__,_/_/ \__,_/_/ > > Apache Karaf (4.2.0.M2) > > Hit '<tab>' for a list of available commands > and '[cmd] --help' for help on a specific command. > Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown Karaf. > > karaf@root()> > java.lang.RuntimeException: Cannot get the remote bundle context > > at org.ops4j.pax.exam.rbc.client.intern.RemoteBundleContextClientImpl. > getRemoteBundleContext(RemoteBundleContextClientImpl.java:253) > at org.ops4j.pax.exam.rbc.client.intern.RemoteBundleContextClientImpl. > waitForState(RemoteBundleContextClientImpl.java:210) > at org.ops4j.pax.exam.karaf.container.internal.KarafTestContainer. > waitForState(KarafTestContainer.java:655) > at org.ops4j.pax.exam.karaf.container.internal. > KarafTestContainer.startKaraf(KarafTestContainer.java:258) > at org.ops4j.pax.exam.karaf.container.internal.KarafTestContainer.start( > KarafTestContainer.java:191) > at org.ops4j.pax.exam.spi.reactors.PerClassStagedReactor.setUp( > PerClassStagedReactor.java:55) > at org.ops4j.pax.exam.spi.reactors.PerClassStagedReactor.beforeClass( > PerClassStagedReactor.java:90) > at org.ops4j.pax.exam.spi.reactors.ReactorManager. > beforeClass(ReactorManager.java:388) > at org.ops4j.pax.exam.junit.DriverExtension.beforeClassBlock( > DriverExtension.java:129) > at org.ops4j.pax.exam.junit.ExtensibleRunner$1.evaluate( > ExtensibleRunner.java:53) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.ops4j.pax.exam.junit.PaxExam.run(PaxExam.java:78) > at org.junit.runner.JUnitCore.run(JUnitCore.java:137) > at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs( > JUnit4IdeaTestRunner.java:68) > at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater. > startRunnerWithArgs(IdeaTestRunner.java:47) > at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart( > JUnitStarter.java:242) > at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70) > Caused by: java.rmi.NotBoundException: e6a516a9-b9af-4fca-92e2- > 255ca5ba835f > at sun.rmi.registry.RegistryImpl.lookup(RegistryImpl.java:209) > at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source) > at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:450) > at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) > at sun.rmi.transport.Transport$1.run(Transport.java:200) > at sun.rmi.transport.Transport$1.run(Transport.java:197) > at java.security.AccessController.doPrivileged(Native Method) > at sun.rmi.transport.Transport.serviceCall(Transport.java:196) > at sun.rmi.transport.tcp.TCPTransport.handleMessages( > TCPTransport.java:568) > at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0( > TCPTransport.java:826) > at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$ > 0(TCPTransport.java:683) > at java.security.AccessController.doPrivileged(Native Method) > at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run( > TCPTransport.java:682) > at java.util.concurrent.ThreadPoolExecutor.runWorker( > ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run( > ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer( > StreamRemoteCall.java:276) > at sun.rmi.transport.StreamRemoteCall.executeCall( > StreamRemoteCall.java:253) > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:379) > at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source) > at org.ops4j.pax.exam.rbc.client.intern.RemoteBundleContextClientImpl. > getRemoteBundleContext(RemoteBundleContextClientImpl.java:240) > ... 16 more > > > Test ignored. > > Den torsdag den 24. august 2017 kl. 10.51.42 UTC+2 skrev Martin Lichtin: >> >> 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.ad >> dingEntries(TestBundleObserver.java:69)[296:org.ops4j.pax. >> exam.extender.service:4.11.0] >> at org.ops4j.pax.swissbox.extender.BundleWatcher$3.run(BundleWa >> tcher.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$ScheduledFu >> tureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_141] >> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFu >> tureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_141] >> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool >> Executor.java:1149)[:1.8.0_141] >> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo >> lExecutor.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 a topic in the > Google Groups "OPS4J" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/ops4j/L4KLkKzQOwM/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Best regards / Med venlig hilsen Nino Martinez -- -- ------------------ 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.
