|Cannot connect to VM for debugging, AVast Security the culprit [message #1184516]
||Wed, 13 November 2013 14:04
| Gary Worsham
Registered: September 2013
This didn't used to be the case and I am not sure what it was exactly that changed between when it worked and now that it doesn't. I'm stopped dead in my tracks on development for almost a week now.|
I've read many posts, most of them several years old, describing the exact error message:
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
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:750]
Some suspicion it is related to firewall. I disabled my Avast firewall (by turning it off in the UI and ultimately, stopping the service), didn't make a difference. I did then get a pop up from Windows firewall asking for permission to allow traffic, which I did. Didn't help.
I re enabled Avast and opened TCP in/out on 127.0.0.1 and "localhost".
I'm still not convinced it ISN'T something to do with the firewall but it seems I need a more elaborate debugging strategy. Any pointers? I'm trying just about everything I can find on Google, such as restart the machine, reinstall Eclipse, use JDK instead of JRE, etc.
I don't know how to test my firewall setting independent of Eclipse. Any advice and or wild guesses welcome.
I'm using Windows 7 32 bit. JRE/JDK 1.7.
[Updated on: Wed, 13 November 2013 14:43]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.03196 seconds