On Tue, Jun 15, 2010 at 11:18 AM, Simon Laws <[email protected]> wrote:
> On Mon, Jun 14, 2010 at 1:36 PM, kelvin goodson
> <[email protected]> wrote:
>> Has anyone seen failures like I'm seeing below? I updated from both
>> oasis and apache svn in the last hour.
>> I get 58 failures in otest assembly tests (under newlayout)
>>
>>  the failure is in each case a ConnectException  As far as I can see
>> the failure is in accessing localhost/127.0.0.1:9080
>>
>> Kelvin.
>>
>> Running client.ASM_5034_TestCase
>> Implementation language set to: _Java
>> <snip>
>> INFO: Added Servlet mapping:
>> http://9.146.215.194:8080/TestComponent2/Service1/second
>> 14-Jun-2010 13:24:51
>> org.apache.tuscany.sca.core.assembly.impl.EndpointRegistryImpl
>> addEndpoint
>> INFO: Add endpoint - (@7228326)Endpoint:  URI =
>> TestComponent2#service-binding(Service1/second)
>> Exception received - detail: HTTP transport error:
>> java.net.ConnectException: Connection refused: connect
>> com.sun.xml.ws.client.ClientTransportException: HTTP transport error:
>> java.net.ConnectException: Connection refused: connect
>>        at 
>> com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:132)
>>        at 
>> com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:153)
>>        at 
>> com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:94)
>>        at 
>> com.sun.xml.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:116)
>>        at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:598)
>>        at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:557)
>>        at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:542)
>>        at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:439)
>>        at com.sun.xml.ws.client.Stub.process(Stub.java:222)
>>        at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:135)
>>        at 
>> com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:109)
>>        at 
>> com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)
>>        at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118)
>>        at $Proxy41.invokeTest(Unknown Source)
>>        at client.BaseJAXWSTestRunner.invokeTest(BaseJAXWSTestRunner.java:213)
>>        at client.BaseJAXWSTestRunner.testDummy(BaseJAXWSTestRunner.java:170)
>>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>>        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>>        at java.lang.reflect.Method.invoke(Unknown Source)
>>        at 
>> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
>>        at 
>> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>>        at 
>> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
>>        at 
>> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>>        at 
>> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
>>        at 
>> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
>>        at 
>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:73)
>>        at 
>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:46)
>>        at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180)
>>        at org.junit.runners.ParentRunner.access$000(ParentRunner.java:41)
>>        at org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173)
>>        at 
>> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
>>        at 
>> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
>>        at org.junit.runners.ParentRunner.run(ParentRunner.java:220)
>>        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.net.ConnectException: Connection refused: connect
>>        at java.net.PlainSocketImpl.socketConnect(Native Method)
>>        at java.net.PlainSocketImpl.doConnect(Unknown Source)
>>        at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
>>        at java.net.PlainSocketImpl.connect(Unknown Source)
>>        at java.net.SocksSocketImpl.connect(Unknown Source)
>>        at java.net.Socket.connect(Unknown Source)
>>        at java.net.Socket.connect(Unknown Source)
>>        at sun.net.NetworkClient.doConnect(Unknown Source)
>>        at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>        at sun.net.www.http.HttpClient.openServer(Unknown Source)
>>        at sun.net.www.http.HttpClient.<init>(Unknown Source)
>>        at sun.net.www.http.HttpClient.New(Unknown Source)
>>        at sun.net.www.http.HttpClient.New(Unknown Source)
>>        at 
>> sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
>>        at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown 
>> Source)
>>        at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
>>        at 
>> sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
>>        at 
>> com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:120)
>>        ... 39 more
>>
>
> I think this is an OASIS problem. Looks like some test configuration
> was committed to their svn. I'll ask Mike.
>
> Simon
>
> --
> Apache Tuscany committer: tuscany.apache.org
> Co-author of a book about Tuscany and SCA: tuscanyinaction.com
>

OK I talked to Mike and he's removes the offending configuration. I
still see 7 failures in the 8xxx range but there are related to
callback fixes I believe so I'm looking at them.

Simon

-- 
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com

Reply via email to