Community
Participate
Working Groups
What steps will reproduce the problem? I can't tell how to reproduce it exactly, but but looking at teh web, this is a pretty common bug: I launch a program in debug mode and get that error. Even the infamous "hello world" program would not launch I've found the solution though: the default jre I use is a jdk. And in jdk/bin, there was missing the dt_socket.dll file. I copied it from "jkd/jre/bin" back into "jdk/bin" and it worked! After a lot of looking around, I found the solution in an old bug that was closed in 2007 Bug 176471 - [launching] debug fails if the default jre is a jdk . It seems this problem is back ! -- Error Details -- Date: Tue Dec 01 15:44:15 CET 2015 Message: Cannot connect to VM Severity: Error Product: Eclipse 4.5.1.20150917-1200 (org.eclipse.epp.package.java.product) Plugin: org.eclipse.jdt.launching Session Data: eclipse.buildId=4.5.1.M20150904-0015 java.version=1.7.0_79 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=fr_FR Framework arguments: -product org.eclipse.epp.package.java.product -product org.eclipse.epp.package.java.product Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.java.product -data file:/C:/Users/elouanl/workspace/ -product org.eclipse.epp.package.java.product Exception Stack Trace: java.net.SocketException: Socket operation on nonsocket: configureBlocking at java.net.DualStackPlainSocketImpl.configureBlocking(Native Method) at java.net.DualStackPlainSocketImpl.socketAccept(DualStackPlainSocketImpl.java:141) at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:398) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:199) at java.net.ServerSocket.implAccept(ServerSocket.java:530) at java.net.ServerSocket.accept(ServerSocket.java:498) at org.eclipse.jdi.internal.connect.SocketTransportService.accept(SocketTransportService.java:103) at org.eclipse.jdi.internal.connect.SocketTransportImpl.accept(SocketTransportImpl.java:60) at org.eclipse.jdi.internal.connect.SocketListeningConnectorImpl.accept(SocketListeningConnectorImpl.java:157) at org.eclipse.jdt.internal.launching.StandardVMDebugger$ConnectRunnable.run(StandardVMDebugger.java:112) at java.lang.Thread.run(Thread.java:745)
Which different java versions are you using ? As we have a workaround, reducing the Severity.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
myEclipse has this error problem Occurred "Cannot connect to VM Socket operation on nonsocket: configureBlocking"; console display : "Error occurred during initialization of boot layer java.lang.module.FindException: Unable to derive module descriptor for C:\Users\TechCare\Downloads\Compressed\spring-framework-4.1.6.RELEASE\libs\spring-web-4.1.6.RELEASE-sources.jar Caused by: java.lang.module.InvalidModuleDescriptorException: Provider class org.springframework.web.SpringServletContainerInitializer not in module". please help me !!
(In reply to Nguyễn Quốc Kiệt from comment #3) > myEclipse has this error > > problem Occurred "Cannot connect to VM > Socket operation on nonsocket: configureBlocking"; > > console display : "Error occurred during initialization of boot layer > java.lang.module.FindException: Unable to derive module descriptor for > C:\Users\TechCare\Downloads\Compressed\spring-framework-4.1.6. > RELEASE\libs\spring-web-4.1.6.RELEASE-sources.jar > Caused by: java.lang.module.InvalidModuleDescriptorException: Provider class > org.springframework.web.SpringServletContainerInitializer not in module". > please help me !! Can you check the Installation details to see the Eclipse and any steps to help?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
