| Debug Error: Cannot Connect to VM [message #504852] |
Tue, 22 December 2009 23:50  |
Eclipse User |
|
|
|
I get this error when I try to debug any application
Cannot connect to VM
com.sun.jdi.connect.TransportTimeoutException
at org.eclipse.jdi.internal.connect.SocketTransportService.acce pt(SocketTransportService.java:97)
at org.eclipse.jdi.internal.connect.SocketTransportImpl.accept( SocketTransportImpl.java:56)
at org.eclipse.jdi.internal.connect.SocketListeningConnectorImp l.accept(SocketListeningConnectorImpl.java:135)
at org.eclipse.jdt.internal.launching.StandardVMDebugger$Connec tRunnable.run(StandardVMDebugger.java:107)
at java.lang.Thread.run(Thread.java:636)
Then on the terminal I get this:
ERROR: transport error 202: connect failed: Connection timed out
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
As far as I can tell, my debug and run configurations are exactly the same (they use the same VM). What could be the problem?
Thanks,
Eric
|
|
|
|
|
| Re: Debug Error: Cannot Connect to VM [message #990240 is a reply to message #505066] |
Tue, 11 December 2012 09:40  |
| Eclipse User |
|
|
|
Eric Kulcyk wrote on Sat, 26 December 2009 01:27Hey,
I figured it out! I accidently changed my /etc/network/interfaces file before. The reason is wasn't working was because the following lines weren't in that file:
auto lo
iface lo inet loopback
Once I put those line back in and restarted, it fixed the problem. If that doesn't work for you, i think it might be another networking problem.
Good luck to whoever else runs into this problem,
Eric
Had to sign up to say thank you for this reply.
I had been following the route of ipv6 bindings with no luck.
Many thanks
|
|
|
Powered by
FUDForum. Page generated in 0.09946 seconds
Home