java.net.SocketException

Connection reset by peer: socket write error [5/23/07 14:47:20:906 CST] 17dd17dd SystemErr R at java.lang.Throwable.<init>(Throwable.java:52) [5/23/07 14:47:20:906 CST] 17dd17dd SystemErr R at java.lang.Throwable.<init>(Throwable.java:66) [5/23/07 14:47:20:906 CST] 17dd17dd SystemErr R at java.net.SocketException.<init>(SocketException.java:46)

Samebug tips9

Upgrade your docker-selenium

Client closed the websocket connection (safe to ignore)

Don't give up yet. Our experts can help. Paste your full stack trace to get a solution.

Solutions on the web9320

  • via Oracle Community by 843844, 11 months ago
    Connection reset by peer: socket write error [5/23/07 14:47:20:906 CST] 17dd17dd SystemErr R at java.lang.Throwable.<init>(Throwable.java:52) [5/23/07 14:47:20:906 CST] 17dd17dd SystemErr R at java.lang.Throwable.<init>(Throwable.java:66) [5/23/07 14:47:20:906 CST] 17dd17dd SystemErr R at java.net.SocketException.<init>(SocketException.java:46)
  • A connection with a remote socket was reset by that at java.lang.Throwable.&lt;init&gt;(Throwable.java:195) at java.lang.Exception.&lt;init&gt;(Exception.java:41) at java.io.IOException
  • via https://bugzilla.redhat.com/bugzilla/ by Toshiya Kobayashi, 1 year ago
    Connection reset by peer: socket write error^M 2012-07-27 14:41:42,469 ERROR [STDERR] (http-0.0.0.0-8080-8) at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:402)
  • Stack trace

    • java.net.SocketException: Connection reset by peer: socket write error [5/23/07 14:47:20:906 CST] 17dd17dd SystemErr R at java.lang.Throwable.<init>(Throwable.java:52) [5/23/07 14:47:20:906 CST] 17dd17dd SystemErr R at java.lang.Throwable.<init>(Throwable.java:66) [5/23/07 14:47:20:906 CST] 17dd17dd SystemErr R at java.net.SocketException.<init>(SocketException.java:46) at java.net.SocketOutputStream.socketWrite(Native Method) at java.net.SocketOutputStream.write(SocketOutputStream.java:103) at com.ibm.ws.io.Stream.write(Stream.java:26) at com.ibm.ws.io.WriteStream.flushMyBuf(WriteStream.java:145) at com.ibm.ws.io.WriteStream.write(WriteStream.java:119) at com.ibm.ws.http.ResponseStream.writeChunk(ResponseStream.java:289) at com.ibm.ws.http.ResponseStream.flushBuffer(ResponseStream.java:215) at com.ibm.ws.http.ResponseStream.write(ResponseStream.java:143) at com.ibm.ws.io.WriteStream.write(WriteStream.java:102) at com.ibm.ws.webcontainer.http.HttpConnection.write(HttpConnection.java:362) at com.ibm.ws.webcontainer.srp.SRPConnection.write(SRPConnection.java:224) at com.ibm.ws.webcontainer.srt.SRTOutputStream.write(SRTOutputStream.java:89) at com.ibm.ws.webcontainer.srt.BufferedServletOutputStream.writeOut(BufferedServletOutputStream.java:443) at com.ibm.ws.webcontainer.srt.BufferedServletOutputStream.write(BufferedServletOutputStream.java:309) at java.io.OutputStream.write(OutputStream.java:75) at ph.gov.da.finalstandards.actions.Word.doPost(Word.java:154) at ph.gov.da.finalstandards.actions.Word.doGet(Word.java:78) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110) at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174) at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313) at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116) at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283) at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42) at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:1030)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 3 days ago
    Unknown user
    Once, 3 days ago
    Unknown user
    Once, 3 days ago
    Unknown user
    Once, 3 days ago
    Unknown user
    Once, 1 week ago
    159 more bugmates