Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Newcomers » Newcomers » Debug Error: Cannot Connect to VM
Debug Error: Cannot Connect to VM [message #504852] Tue, 22 December 2009 23:50 Go to next message
Eric Kulcyk is currently offline Eric Kulcyk
Messages: 4
Registered: September 2009
Junior Member
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 #505060 is a reply to message #504852] Fri, 25 December 2009 18:55 Go to previous messageGo to next message
Eclipse User
Originally posted by: gunnar.stahl.gunnarstahl.org

Hi, ran into a similar problem today. On debian testing the Java networking was completely disabled. Check out the following URL if you use debian testing:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560056

Yt, Gunnar

erickulcyk@gmail.com schrieb:
> 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 #505066 is a reply to message #505060] Sat, 26 December 2009 01:27 Go to previous messageGo to next message
Eric Kulcyk is currently offline Eric Kulcyk
Messages: 4
Registered: September 2009
Junior Member
Hey,

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
Re: Debug Error: Cannot Connect to VM [message #990240 is a reply to message #505066] Tue, 11 December 2012 09:40 Go to previous message
James McDines is currently offline James McDines
Messages: 1
Registered: December 2012
Junior Member
Eric Kulcyk wrote on Sat, 26 December 2009 01:27
Hey,

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
Previous Topic:Re: Java Project Question
Next Topic:Lua eclipse
Goto Forum:
  


Current Time: Fri Apr 18 11:46:47 EDT 2014

Powered by FUDForum. Page generated in 0.02109 seconds