java.net.SocketException

Software caused connection abort: socket write error

Samebug tips13

Upgrade your docker-selenium

Probably there is a bug in TestNG Eclipse plugin (6.8.6.20130607_0745), try an other version (e.g. 6.8.0.20121120_1820)

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

Solutions on the web8864

  • via Google Groups by praveen, 1 month ago
    Software caused connection abort: socket write error
  • via JIRA by Maciej Michalak, 3 months ago
    Software caused connection abort: socket write error
  • via Pentaho BI Platform Tracking by Jared Pshedesky, 1 year ago
    Software caused connection abort: socket write error
  • Stack trace

    • java.net.SocketException: Software caused connection abort: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(Unknown Source) at java.net.SocketOutputStream.write(Unknown Source) at java.io.BufferedOutputStream.flushBuffer(Unknown Source) at java.io.BufferedOutputStream.flush(Unknown Source) at java.io.DataOutputStream.flush(Unknown Source) at org.mule.transport.tcp.protocols.LengthProtocol.writeByteArray(LengthProtocol.java:96) at org.mule.transport.tcp.protocols.AbstractByteProtocol.write(AbstractByteProtocol.java:81) at org.mule.transport.tcp.protocols.AbstractByteProtocol.write(AbstractByteProtocol.java:77) at org.mule.transport.tcp.protocols.SafeProtocol.write(SafeProtocol.java:56) at org.mule.transport.tcp.TcpMessageReceiver$TcpWorker.handleResults(TcpMessageReceiver.java:412) at org.mule.transport.AbstractReceiverWorker.doRun(AbstractReceiverWorker.java:132) at org.mule.transport.AbstractReceiverResourceWorker.doRun(AbstractReceiverResourceWorker.java:51) at org.mule.transport.AbstractReceiverWorker.run(AbstractReceiverWorker.java:62) at org.mule.work.WorkerContext.run(WorkerContext.java:310) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575) at java.lang.Thread.run(Unknown Source)

    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, 1 year ago
    Once, 2 months ago
    2 times, 2 months ago
    Unknown user
    Once, 10 months ago
    Unknown user
    Once, 1 year ago
    216 more bugmates