[ 
https://issues.apache.org/activemq/browse/CAMEL-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51346#action_51346
 ] 

Willem Jiang commented on CAMEL-1561:
-------------------------------------

This issue relates to the PAXRUNNER-233[1], this issue has been resolved in PAX 
runner 0.19.0, and PAX-Exam 0.5.0-SNAPSHOT uses this version of PAX-Runner.
So we need to update to PAX-Exam to 0.5.0 which will be released soon, before 
that I'd like to upgrade the PAX-Exam to 0.5.0-SNAPSHOT.

I will keep this issue open until we can use PAX-Exam 0.5.0.

[1] http://issues.ops4j.org/browse/PAXRUNNER-233

> camel-itest-osgi can't run successfully in windows
> --------------------------------------------------
>
>                 Key: CAMEL-1561
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1561
>             Project: Apache Camel
>          Issue Type: Test
>          Components: tests
>            Reporter: Willem Jiang
>            Assignee: Willem Jiang
>
> I got the below error when I run the camel-itest-osgi in my windows box.
> > org.ops4j.pax.exam.spi.container.TestContainerException: Cannot get the
> > remote bundle context
> >     at
> > org.ops4j.pax.exam.rbc.client.RemoteBundleContextClient.getRemoteBundleContext(RemoteBundleContextClient.java:256)
> >     at
> > org.ops4j.pax.exam.rbc.client.RemoteBundleContextClient.stop(RemoteBundleContextClient.java:201)
> >     at
> > org.ops4j.pax.exam.container.def.internal.PaxRunnerTestContainer.stop(PaxRunnerTestContainer.java:160)
> >     at
> > org.ops4j.pax.exam.junit.internal.JUnit4TestMethod.invoke(JUnit4TestMethod.java:120)
> >     at
> > org.junit.internal.runners.MethodRoadie.runTestMethod(MethodRoadie.java:105)
> >     at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:86)
> >     at
> > org.ops4j.pax.exam.junit.internal.JUnit4MethodRoadie.runBeforesThenTestThenAfters(JUnit4MethodRoadie.java:60)
> >     at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:84)
> >     at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:49)
> >     at
> > org.ops4j.pax.exam.junit.JUnit4TestRunner.invokeTestMethod(JUnit4TestRunner.java:245)
> >     at
> > org.ops4j.pax.exam.junit.JUnit4TestRunner.runMethods(JUnit4TestRunner.java:195)
> >     at
> > org.ops4j.pax.exam.junit.JUnit4TestRunner$2.run(JUnit4TestRunner.java:185)
> >     at
> > org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:34)
> >     at 
> > org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:44)
> >     at 
> > org.ops4j.pax.exam.junit.JUnit4TestRunner.run(JUnit4TestRunner.java:181)
> >     at
> > org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:45)
> >     at
> > org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> >     at
> > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
> >     at
> > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
> >     at
> > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
> >     at
> > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
> > Caused by: java.rmi.ConnectException: Connection refused to host:
> > 192.168.0.131; nested exception is:
> >     java.net.ConnectException: Connection refused: connect
> >     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:574)
> >     at 
> > sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
> >     at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
> >     at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
> >     at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
> >     at
> > org.ops4j.pax.exam.rbc.client.RemoteBundleContextClient.getRemoteBundleContext(RemoteBundleContextClient.java:234)
> >     ... 20 more
> > Caused by: java.net.ConnectException: Connection refused: connect
> >     at java.net.PlainSocketImpl.socketConnect(Native Method)
> >     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
> >     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
> >     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
> >     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
> >     at java.net.Socket.connect(Socket.java:520)
> >     at java.net.Socket.connect(Socket.java:470)
> >     at java.net.Socket.<init>(Socket.java:367)
> >     at java.net.Socket.<init>(Socket.java:180)
> >     at
> > sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
> >     at
> > sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
> >     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569)
> >     ... 25 more

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to