- This topic has 5 replies, 2 voices, and was last updated 16 years, 1 month ago by
.
-
Posts
-
When debugging a Java Swing application developed with MyEclipse 7.0 release 2 installed with Pulse in Linux I got the following message::
Cannot connect to VM
com.sun.jdi.connect.TransportTimeoutExceptionAfter a while, the VM dies and the console brings these further messages:
ERROR: transport error 202: handshake failed - received ><!DOCTYPE HTML< - excepted >JDWP-Handshake< FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197) 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]It happens with both VMs installed: the 1.5 version installed by pulse and the Sun Java 6 version installed in my Linux distro.
Did I do something wrong in my installation?
Thanks,
VÃtor Souza
I thought it could be a bug in 7.0 because it’s still Milestone 2 and not final, then I installed 6.5 Pulse Edition and the same thing happened…
Thanks,
VÃtor Souza
I thought it could be a bug in 7.0 because it’s still Milestone 2 and not final, then I installed 6.5 Pulse Edition and the same thing happened…
Thanks,
VÃtor Souza
Are you behind a firewall ?
Are you using a launch configuration?
Can you go to MyEclipse > Installation Summary > installation Details and paste the information here for me.
@support-nipun wrote:
Are you behind a firewall ?
Hmmmm… Sorry for being so lame 🙂 I never though that the network could be in the way of connecting to a local VM, but…
I use a software called u2nl, which redirects my network Internet traffic through the proxy that we use here at the University. I just realized I didn’t include an exception for local IP addresses.
I shut down the u2nl and debug worked. I’ll work on the exception rule now. Thanks a lot.
Vitor
