Eclipse Oxigen5 - "Cannot connect to VM Socket operation on nonsocket: configureBlocking"

Question

I'm receiving following error message when trying to debug a project on Eclipse Oxygen5:

This Eclipse installation was made on a new machine along with JDK1.8.0_144 and JRE1.8.0_144. I then copied the workspace folder containing the project and placed it in the new machine, where I opened it with Eclipse. Everything seems fine, it runs the project normally, but when I click on debug, it gives me the error. I tried searching for a solution to this issue and came across multiple posts of people having similar problems, but nothing worked. The machine is running under Windows 10 Pro x64 (10.0, Compilation: 14393).

EDIT: I should also mention that I'm connected to this machine via TeamViewer. I transferred the project to the new machine using TeamViewer and opened it's root folder as the workspace folder when Eclipse was launched. I already tried uninstalling everything and reinstalling it.

Answer 1

I had the same problem. After investigating, I've found that removing my debug configurations fixes the problem. So, in your debug config, remove Xrunjdwp:transport=dt_socket,suspend=n,address=8000,server=y

Answer 2

Deleting and re-importing project in the eclipse worked for me.

Answer 3

I had a same or similar problem with latest Eclipse-2019-12-R + I had in the console:

Error opening zip file or JAR manifest missing : D:\
Error occurred during initialization of VM
agent library failed to init: instrument

The problem was caused by the '=' character in the path to the eclipse:

D:\=folder_name=\...\eclipse

Interesting is that older Eclipse (Oxygen3a) hasn't this problem.

Answer 4

I had the same problem, and, after uninstalling JRE/JDK, recovering Eclipse files and a whole afternoon of research, I found that the error "Cannot connect to VM Socket operation on nonsocket: configureBlocking" didn't happen anymore after changing my default output folder from a linked resource to a local folder.

Instructions for changing the default output folder here.

Answer 5

In Brazil Warsaw cause this error on eclipse.

You can uninstall Warsaw from your computer by using the Add/Remove Program feature in the Window's Control Panel.

This solved my problem.

Answer 6

I had the same problem...

Create a new java project, make a new simple class (main and sysout) and try to run debug. If it works then the problem is in the project.

Considering that problem is in the project do this:

1. Delete files in ".settings" folder, inside project folder.
2. Remake facets in project settings.

Try debug your project.

Answer 7

I got a similar error because i had set the initial size of the heap grater than the maximal amount assigned (on a jboss server).

-server -Xms2048m -Xmx1024m to -server -Xms2048m -Xmx2048m

Answer 8

I had the same error and I could fix it selecting another JRE to run the application, i.e., the project JRE instead of a custom JRE.