And I close the socket only in one place, when I removed it, nothing has changed not counting auto-closing try with resources But I do not close the server socket. I'm looking at your Server class in the finally clause.
Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Related Hot Network Questions. Question feed. Stack Overflow works best with JavaScript enabled. You can choose which cookies you want to accept.
We need basic cookies to make this site work, therefore these are the minimum you can select. Like Quote Share. This topic has been closed for comments. Did you find what you're looking for?
If not: Ask the community for help! Ask your question here. Powered by inSided. Sign up Already have an account? Username Do not use your email as a username. Email Address Use your work email address. Login to the community No account yet?
Username or Email. Remember me. Forgot password? After updated the plugin to the version 6. The text was updated successfully, but these errors were encountered:. Sorry, something went wrong. How can I downgrade to 6. On Fri, May 22, at AM, atul notifications github. Eclipse is running via 1. Is this what you mean? If so, I can't really update my project to 1. OK then, the minimum jdk version required by testng 6. So could you run it with 1. Just hit this error again on a new Eclipse Mars install.
Running against a project targeted at 1. Brand new setup! Surely others are hitting this. I can confirm. This is happening to me again but even downgrading did not help me.
The stack trace is as follows:. SocketException: Software caused connection abort: socket write error at java. The testng version I use as a dependency is 6. Project conforms to 1. Testng version is 6.
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. This is a maven project which I switch between Eclipse and Netbeans due to lack of support for mybatis in netbeans. I deprecated the string protocol because it was not flexible and it was written quickly for the 1. 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? For Eclipse Luna 4. I confirm, I had to do the same. But mostly for previous generations of TestNG 6.
0コメント