Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

  1. ,
    via github.com by Unknown author

    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)

  2. ,
    via GitHub by ppoulard

    before running my test in debug mode, i open the debug view, and remove some breakpoints (such as some remaining on NullPointersExceptions, and Sockets)

Solutions on the web

via Coderanch by Shishir Jain, 1 year ago
Software caused connection abort: socket write error
via Stack Overflow by user1053540
, 2 years ago
Software caused connection abort: socket write error
via GitHub by krampstudio
, 1 year ago
Software caused connection abort: socket write error
via Google Groups by AnthonyK, 2 years ago
Software caused connection abort: socket write error
via Stack Overflow by Duncan Palmer
, 2 years ago
Software caused connection abort: socket write error
via Stack Overflow by user760220
, 2 years ago
Software caused connection abort: socket write error
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.ObjectOutputStream$BlockDataOutputStream.drain(Unknown Source)	at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(Unknown Source)	at java.io.ObjectOutputStream.writeNonProxyDesc(Unknown Source)	at java.io.ObjectOutputStream.writeClassDesc(Unknown Source)	at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source)	at java.io.ObjectOutputStream.writeObject0(Unknown Source)	at java.io.ObjectOutputStream.writeFatalException(Unknown Source)	at java.io.ObjectOutputStream.writeObject(Unknown Source)	at org.testng.remote.strprotocol.SerializedMessageSender.sendMessage(SerializedMessageSender.java:21)	at org.testng.remote.strprotocol.MessageHub.sendMessage(MessageHub.java:44)	at org.testng.remote.strprotocol.RemoteTestListener.onTestStart(RemoteTestListener.java:49)	at org.testng.internal.Invoker.runTestListeners(Invoker.java:1805)	at org.testng.internal.Invoker.runTestListeners(Invoker.java:1780)	at org.testng.internal.Invoker.invokeMethod(Invoker.java:643)	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:846)	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1170)	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)	at org.testng.TestRunner.runWorkers(TestRunner.java:1147)	at org.testng.TestRunner.privateRun(TestRunner.java:749)	at org.testng.TestRunner.run(TestRunner.java:600)	at org.testng.SuiteRunner.runTest(SuiteRunner.java:317)	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:312)	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:274)	at org.testng.SuiteRunner.run(SuiteRunner.java:223)	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1039)	at org.testng.TestNG.runSuitesLocally(TestNG.java:964)	at org.testng.TestNG.run(TestNG.java:900)	at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:110)	at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:205)	at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:174)