Related information:
Eclipse 32-bit
----------------------------------
Eclipse Standard/SDK
Version: Luna Release (4.4.0)
Build id: 20140612-0600
JDK 1.8 local installation 32-bit
----------------------------------
java version "1.8.0_11"
Java(TM) SE Runtime Environment (build 1.8.0_11-b12)
Java HotSpot(TM) Client VM (build 25.11-b03, mixed mode, sharing)
Operating system W7 64 bit
-----------------------------------
TestNG 6.1.1
-----------------------------------
TestNG Eclipse Plug-in is up to date
-----------------------------------
Error message:
java.net.SocketException: Software caused connection abort: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1676)
at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(ObjectOutputStream.java:1585)
at java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1167)
at java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1121)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1278)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1073)
at java.io.ObjectOutputStream.writeFatalException(ObjectOutputStream.java:1392)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:294)
at org.testng.remote.strprotocol.SerializedMessageSender.sendMessage(SerializedMessageSender.java:25)
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:1904)
at org.testng.internal.Invoker.runTestListeners(Invoker.java:1879)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:685)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
at org.testng.TestRunner.privateRun(TestRunner.java:767)
at org.testng.TestRunner.run(TestRunner.java:617)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1198)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1123)
at org.testng.TestNG.run(TestNG.java:1031)
at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:111)
at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:204)
at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:175)
The most wonderful thing is that it has been tested. What to do, to install 1.7 of the JRE or JDK, modify the local Jdk&jre point. Navigate to 1.7, restart.
If there is still a problem with the Eclipse installation directory, find Eclipse.ini last append-dtestng.eclipse.verbose=true. Reboot.
Well, the beginning I switched to 1.7 still does not solve the problem, added-dtestng.eclipse.verbose=true resolution. Looking back at the test, found that the removal of this parameter is also normal. May be a factor in eclipse's slowness.
Thanks to Git's great god here.
Socketexception:software caused connection abort #91
Https://github.com/cbeust/testng-eclipse/issues/91
Feel the high version of the JDK with less, should other versions also encounter this problem. The 13 issue has not turned off T-t ~
TestNG 6.1.1 + Eclipse Luna 4.4.0 + TestNG Eclipse plugin Error