On Wed, Jul 30, 2008 at 10:31 AM, Ramkumar Ramalingam (JIRA) <
[email protected]> wrote:

> 1.3RC3 - WSDLless itest fails with SocketException: Operation timed out
> -----------------------------------------------------------------------
>
>                 Key: TUSCANY-2518
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2518
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Integration Tests
>    Affects Versions: Java-SCA-1.3
>         Environment: Windows XP, IBM JDK 1.5 SR4
>            Reporter: Ramkumar Ramalingam
>             Fix For: Java-SCA-1.3
>
>
> Tried running "mvn clean install" with 1.3RC3 source distribution and saw
> the following test failure in WSDLless itests.....
>
> <testcase time="21.75" name="testGetUsingMoreComplexObject">
>    <error type="com.sun.xml.ws.client.ClientTransportException"
> message="HTTP transport error: java.net.SocketException: Operation timed
> out: connect:could be due to invalid
> address">com.sun.xml.ws.client.ClientTransportException: HTTP transport
> error: java.net.SocketException: Operation timed out: connect:could be due
> to invalid address
>        at
> com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:131)
>        at
> com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:151)
>        at
> com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:93)
>        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 $Proxy87.getUsingString(Unknown Source)
>        at
> service.SomeComponentTestCase.testGetUsingMoreComplexObject(SomeComponentTestCase.java:60)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
>        at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>        at java.lang.reflect.Method.invoke(Method.java:615)
>        at
> org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
>        at
> org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
>        at
> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
>        at
> org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
>        at
> org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
>        at
> org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75)
>        at
> org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36)
>        at
> org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
>        at
> org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
>        at
> org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
>        at
> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
>        at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
>        at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
>        at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
>        at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>        at java.lang.reflect.Method.invoke(Method.java:615)
>        at
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
>        at
> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
> Caused by: java.net.SocketException: Operation timed out: connect:could be
> due to invalid address
>        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:372)
>        at
> java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:233)
>        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:220)
>        at java.net.Socket.connect(Socket.java:541)
>        at java.net.Socket.connect(Socket.java:491)
>        at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
>        at sun.net.www.http.HttpClient.openServer(HttpClient.java:397)
>        at sun.net.www.http.HttpClient.openServer(HttpClient.java:507)
>        at
> sun.net.www.http.HttpClient.&amp;lt;init&amp;gt;(HttpClient.java:245)
>        at sun.net.www.http.HttpClient.New(HttpClient.java:319)
>        at sun.net.www.http.HttpClient.New(HttpClient.java:331)
>        at
> sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:822)
>        at
> sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:801)
>        at
> sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:699)
>        at
> sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:866)
>        at
> com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:119)
>        ... 37 more
>
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
Hi Ram

I just did a "mvn clean install" of the 1.3 RC3 distro on pretty much the
same environment as you, WinXP, IBM JDK5 and it worked OK. Did you have
anything running at the same time that could have caused thr problem. Do you
see the problem if you build just that module?

Simon

Reply via email to