The stack trace shows that the error is coming from HTTPUrlConnection.
Is the JDK version same in both the cases?
-vivek.
Kirk True wrote:
> Hi all,
>
> I'm consistently getting an error when communicating with a SOAP service via JAX-WS 2.1.1.
>
> Here are some details when the error DOES occurs. It does happen when...
>
> * ...using JAX-WS 2.1.1
> * ...client and server are on the same subnet of a gigabit network
> * ...multiple (in this case, 9) threads are hitting the same server at the same time
>
> Here are some details when the error DOESN'T occur. It doesn't happen when...
>
> * ...using Axis2 (the latest version)
> * ...using JWSDP 2.0
> * ...the client and server JVMs are on the same machine
> * ...the client and server are on different networks (i.e. via VPN or on different subnets)
> * ...executing iterations 2..N; only the first time it occurs
> * ...only one client thread is used
>
> Here is the exception:
>
> Caused by: javax.xml.ws.WebServiceException: java.io.IOException: Error writing to server
> at
> com.sun.xml.ws.transport.http.client.HttpClientTransport.checkResponseCode(HttpClientTransport.java:223)
> at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:137)
> at
> com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:74)
> at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:559)
> at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:518)
> at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:503)
> at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:400)
> at com.sun.xml.ws.client.Stub.process(Stub.java:235)
> at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:120)
> at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:230)
> at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:210)
> at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:103)
> at $Proxy34.documentProperties(Unknown Source)
> at com.inxight.uima.LidAnnotator.callSdx(LidAnnotator.java:262)
> at com.inxight.uima.LidAnnotator.process(LidAnnotator.java:122)
> ... 16 more
> Caused by: java.io.IOException: Error writing to server
> at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:421)
> at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:433)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:959)
> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:367)
> at
> com.sun.xml.ws.transport.http.client.HttpClientTransport.checkResponseCode(HttpClientTransport.java:186)
> ... 30 more
>
> Note that from the server's perspective, there are no errors reported.
>
> Any ideas of what could be causing this? We love JAX-WS because it uses (way) less memory than
> Axis2 and is a little faster too. Please let me know if there are any other details, tests, etc. I
> can provide.
>
> Thanks!
> Kirk
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jax-ws.dev.java.net
> For additional commands, e-mail: users-help_at_jax-ws.dev.java.net
>
>