SocketException: Software caused connection abort #91
Comments
|
I experience the same with 6.9.4 on Eclipse 3.6.4. |
|
I am also getting the same error with Eclispe and TestNG Plugin 6.9.4. How can I downgrade to 6.8.1? |
|
Uninstall and install again from the update site: Cédric On Fri, May 22, 2015 at 11:59 AM, atul2710 notifications@github.com wrote:
|
|
I also met this problem after maybe one week not used TestNG plugin. |
|
I'm hitting something similar w/Eclipse 4.4.2, TestNG Eclipse 6.9.5.201506081335: Downgrading to 20141201 seems to fix things. |
|
what's the JDK version you used for running Eclipse and launching the test cases? could you also try with latest snapshot of testng: thanks reference #144 |
|
@missedone The compiler source/target for my project are 1.6. Eclipse is running via 1.8 (I believe). Is this what you mean? If so, I can't really update my project to 1.8 since I have users who are still on 1.6 and 1.7... |
|
OK then, the minimum jdk version required by testng 6.9.5 is 1.7. |
|
No Problem - I guess that's as good a reason as any to force users to move to 1.7 :) |
|
Just hit this error again on a new Eclipse (Mars) install. Running against a project targeted at 1.7. Brand new setup! Surely others are hitting this. Will downgrade the plugin, again. |
|
I can confirm. This is happening to me again but even downgrading did not help me. The stack trace is as follows: java.net.SocketException: Software caused connection abort: socket write error I am on Eclipse Version: Luna Service Release 2 (4.4.2)Build id: 20150219-0600 . The testng version I use as a dependency is 6.8.1. Project conforms to 1.6 and uses 1.7 as jdk. Testng version is 6.8.6.20140201 . I am running it as ordinary user with no admin rights on windows machine due to government policies. Not sure if this is related windows firewall but did not see any popups. This is a failing test. |
|
Upgrading my testng dependency to 6.8.7 fixes the problem. This is a maven project which I switch between Eclipse and Netbeans due to lack of support for mybatis in netbeans. |
|
regards to the testng version, as you are using 6.8.x so it's recommended to use 6.8.21 (the last of 6.8.x) |
|
I had same problems with Eclipse 4.5 (Mars), setting TestNG plugin in "Preferences" to not use the "project TestNG JAR" solved the problem I hope this helps |
|
A more balanced solution, which I was yet unable to test, would be best to upgrade TestNG JAR on project side instead |
|
This issue needs to be fixed. In eclipse Mars is also occurring in version 6.9.5 |
|
I confirm |
|
@eliasbalasis @otavioprado could you try enable String protocol rather than default Object Serialization protocol by adding VM arguments: here is the sample output on Eclipse console: as you can see |
|
@cbeust, in my limit test, i think 'testng.eclipse.stringprotocol' is functional, so i'd like to know why this is second to 'serialization protocol'? what do you think? |
|
I deprecated the string protocol because it was not flexible and it was written quickly for the 1.0 version of the plugin, are you absolutely sure the broken socket comes from the serialization protocol? I'm having a hard time believing that. If I started from scratch today, I would probably use JSON, and maybe it would be pretty trivial to add this (since we already have two protocols, adding a third should be easy). Serialization is easy but fickle since the binary layout of objects can change if the two processes are using different JVM's (which might be the cause for the problem). JSON would make this a non issue, maybe that would be the way to go, what do you think? |
|
yes, i totally agree with the json part, i thought that too, even further, i think it would be a good chance to make testng into multi module:
this can benefit the user that they can better control the dependencies, e.g. for most people they only need testng-core so that they can have a clean dependency tree that wont import unexpected dependent lib (e.g. snakeyaml) anyway, i just jumped to other topic. |
issue #91: add tooltip to 'serialization protocol'
|
For Eclipse Luna (4.4.2), uninstalling TestNG plugin that I had from here: http://beust.com/eclipse and installing with http://beust.com/eclipse-previous worked for me. |
|
I confirm, I had to do the same. -------- Original message -------- For Eclipse Luna (4.4.2), uninstalling TestNG plugin that I had from here: http://beust.com/eclipse and installing with http://beust.com/eclipse-previous worked for me. — |
|
@deshpandeashu and @eliasbalasis did you tried to use string protocol by specifying it in the VM arguments? if you switch to string protocol, do you still have the socket broken pipe issue? |
|
I would love to see the answer to this question too. @missedone has been trying to convince me that switching the protocol would fix the issue and I've been disputing that claim. I would love to be proven wrong so we can finally put this issue behind us :) |
|
@missedone The exception occurs thrice for each test 2015-09-21 19:40:01,078 INFO c.v.v.e.OutcomePrinter [afterInvocation:49] [main] - OUTCOME:PASS java.net.SocketException: Software caused connection abort: socket write error |
|
@missedone i so sorry, i couldn't respond that. I move to another project. So i can't get a print, but the error is pretty similar to the error which the @PriyadharshiniV and @krampstudio post. |
|
@PriyadharshiniV also, as you said "suddenly", do you mean it works well until today even you don not change anything? thanks |
|
@mfpinheiro, no worry, that's still helpful, thanks very much:) |
|
sorry it was working fine till date with a older version of testNG plugin. |
|
Posting the plugin error message in debug mode for TestNG version: 6.9.5.201508210528 [TestNGLaunchConfigurationDelegate] Using the serialized protocol Whereas, with testNG version : 6.8.6.20141201_2240, i dont see this exception "java.io.InvalidClassException: org.testng.remote.strprotocol.TestResultMessage" [TestNGLaunchConfigurationDelegate] Using the serialized protocol |
|
@PriyadharshiniV |
|
@cbeust any comments? |
|
Just want to make sure I understand the solution you propose. Right now, I include the whole testng.jar inside the Eclipse plug-in. You seem to be suggesting to not do that and instead, include a smaller "remote" TestNG jar file with just the remote agent? But you still need testng.jar, right? Adding @juherr to the discussion. |
|
@cbeust |
|
As |
|
@juherr |
|
@cbeust and @juherr |
issue #91: SocketException: Software caused connection abort
issue #91: verify the minimum required version of testng
issue #91: add testng-remote agent jar only for testng version prior to 6.9
|
|
|
@rrbadam |
|
I am seeing the same issue with the latest TestNg plugin. When I connect to my office network it gives me this issue but it works fine with home network. |
|
Sounds like a proxy problem on your work firewall. Cédric On Wed, Feb 10, 2016 at 8:18 AM, kiranyajamanyam notifications@github.com
|
|
I have turned my firewall setting off. Do you have any work around how to fix this issue on Mac. |
|
I dont think we can do anything for this, could you add rule to bypass localhost or 127.0.0.1 in your firewall settings? |
|
Updated my TestNG and Eclipse helped me. current version - |
After updated the plugin to the version 6.8.6.20130607_0745 we get this exception at each test:
By downgrading to 6.8.1 the exception has gone.
The text was updated successfully, but these errors were encountered: