Forum Discussion

Said's avatar
Said
Contributor
4 years ago

java.net.SocketException: Connection reset by peer

Hi All,

 

For a specific request I am getting error below:

Wed Jun 09 10:37:31 CEST 2021: ERROR: java.net.SocketException: Connection reset by peer
   java.net.SocketException: Connection reset by peer
   	at java.base/sun.nio.ch.NioSocketImpl.implWrite(NioSocketImpl.java:420)
   	at java.base/sun.nio.ch.NioSocketImpl.write(NioSocketImpl.java:440)
   	at java.base/sun.nio.ch.NioSocketImpl$2.write(NioSocketImpl.java:826)
   	at java.base/java.net.Socket$SocketOutputStream.write(Socket.java:1051)
   	at com.eviware.soapui.impl.wsdl.support.http.SoapUILoggingOutputStream.write(SoapUILoggingOutputStream.java:41)
   	at org.apache.http.impl.io.SessionOutputBufferImpl.streamWrite(SessionOutputBufferImpl.java:126)
   	at org.apache.http.impl.io.SessionOutputBufferImpl.write(SessionOutputBufferImpl.java:162)
   	at org.apache.http.impl.io.ContentLengthOutputStream.write(ContentLengthOutputStream.java:115)
   	at org.apache.http.entity.ByteArrayEntity.writeTo(ByteArrayEntity.java:116)
   	at org.apache.http.impl.DefaultBHttpClientConnection.sendRequestEntity(DefaultBHttpClientConnection.java:158)
   	at org.apache.http.impl.conn.CPoolProxy.sendRequestEntity(CPoolProxy.java:162)
   	at org.apache.http.protocol.HttpRequestExecutor.doSendRequest(HttpRequestExecutor.java:237)
   	at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$SoapUIHttpRequestExecutor.doSendRequest(HttpClientSupport.java:530)
   	at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:122)
   	at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:271)
   	at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
   	at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
   	at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
   	at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
   	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:71)
   	at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$SoapUIHttpClient.doExecute(HttpClientSupport.java:276)
   	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
   	at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$Helper.execute(HttpClientSupport.java:657)
   	at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport.execute(HttpClientSupport.java:631)
   	at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.submitRequest(HttpClientRequestTransport.java:337)
   	at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.sendRequest(HttpClientRequestTransport.java:254)
   	at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:130)
   	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
   	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
   	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
   	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)
   	at java.base/java.lang.Thread.run(Thread.java:832)

I cannot share the request in this forum, but I can give some details:

  • The error does not occur for all request. Most of them work fine.
  • I got it in a specific case (reproducable). I noticed that one of the values for an element is much longer (164.956 character). The total Message Size in ReadyAPI is: 166220.
  • In case without error the element size around 106.000 characters, but I am not sure length is the cause.

I am using ReadyAPI 3.6. Can someone advice me on this issue? Please tell me if you need additional information.

If needed I can share request with SmartBear support.

 

Thanks in advance!

  • sonya_m's avatar
    sonya_m
    SmartBear Alumni (Retired)
    4 years ago

    Hi Said ! I've found your support ticket about this issue (00480658), looks like this might be something in the app code, please keep working with the team, also, if you find what was causing the issue - share the result here, too! Sure this is going to be useful for community members facing something similar. Thank you.