Community
Participate
Working Groups
M20130814-0800. http://download.eclipse.org/eclipse/downloads/drops4/M20130814-0800/testresults/html/org.eclipse.jdt.debug.tests_linux.gtk.x86_6.0.html Cannot connect to VM org.eclipse.core.runtime.CoreException: Cannot connect to VM at org.eclipse.jdt.launching.AbstractVMRunner.abort(AbstractVMRunner.java:53) at org.eclipse.jdt.internal.launching.StandardVMDebugger.run(StandardVMDebugger.java:374) at org.eclipse.jdt.launching.JavaLaunchDelegate.launch(JavaLaunchDelegate.java:101) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:858) at org.eclipse.jdt.debug.tests.AbstractDebugTest.launchAndWait(AbstractDebugTest.java:973) at org.eclipse.jdt.debug.tests.AbstractDebugTest.launchAndWait(AbstractDebugTest.java:957) at org.eclipse.jdt.debug.tests.AbstractDebugTest.launchToLineBreakpoint(AbstractDebugTest.java:1216) at org.eclipse.jdt.debug.tests.AbstractDebugTest.launchToLineBreakpoint(AbstractDebugTest.java:1200) at org.eclipse.jdt.debug.tests.AbstractDebugTest.launchToLineBreakpoint(AbstractDebugTest.java:1184) at org.eclipse.jdt.debug.tests.state.RefreshStateTests.testAllThreadsSuspended(RefreshStateTests.java:184) at org.eclipse.jdt.debug.tests.AbstractDebugTest.runBare(AbstractDebugTest.java:2389) at org.eclipse.jdt.debug.tests.DebugSuite$1.run(DebugSuite.java:55) at java.lang.Thread.run(Thread.java:662) Caused by: com.sun.jdi.connect.TransportTimeoutException at org.eclipse.jdi.internal.connect.SocketTransportService.accept(SocketTransportService.java:105) at org.eclipse.jdi.internal.connect.SocketTransportImpl.accept(SocketTransportImpl.java:59) at org.eclipse.jdi.internal.connect.SocketListeningConnectorImpl.accept(SocketListeningConnectorImpl.java:153) at org.eclipse.jdt.internal.launching.StandardVMDebugger$ConnectRunnable.run(StandardVMDebugger.java:110)
Moving out of 4.3.1. We can still backport to 4.3.2 if the fix turns out to be safe.
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.
