Debugging problem with Eclipse [message #1165890] |
Fri, 01 November 2013 16:18 |
TMS TMS Messages: 2 Registered: November 2013 |
Junior Member |
|
|
I have suddenly begun getting this weird error when I try to debug any of my projects on Eclipse. I don't remember changing anything for this problem to start so suddenly.
'Launching <my program name>' has encountered a problem.
Cannot connect to VM.
Details of the error:
Cannot connect to VM
com.sun.jdi.connect.TransportTimeoutException
Further, in the console I get the following error:
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]
Please tell me how to solve this problem. I have searched the whole web for an answer but to no luck.
I tried the following solutions which worked for other people:
Restarted Eclipse, restarted computer.
Change hosts file in etc\ - Remove the comments (#) sign before 2 lines namely,
127.0.0.1 localhost
::1 localhost
and restarted.
I read on another forum that a new version of the AVAST firewall could be a problem here.
Thanks
Sousa
[Updated on: Fri, 01 May 2015 16:28] Report message to a moderator
|
|
|
Re: Debugging problem with Eclipse [message #1170382 is a reply to message #1165890] |
Mon, 04 November 2013 15:57 |
TMS TMS Messages: 2 Registered: November 2013 |
Junior Member |
|
|
After much stress and a lot of time, the problem is now resolved.
I uninstalled Eclipse and Java completely from my system.
I then re-installed the latest version of Java (I had this same version previously too). But this time I installed it in the standard directory and not the custom directory that I was using before. I then re-installed Eclipse (latest version again).
I also uninstalled my AVAST 2014 antivirus as people have complained that this was causing problems.
And just like that, it all started working normally again, Debug mode and everything!
[Updated on: Fri, 01 May 2015 16:32] Report message to a moderator
|
|
|
Re: Debugging problem with Eclipse [message #1170456 is a reply to message #1170382] |
Mon, 04 November 2013 17:01 |
|
On 11/4/2013 8:57 AM, Tahir Sousa wrote:
> After much stress and a lot of time, the problem is now resolved. Albeit
> in a very freaky way which does not amuse me as I can't figure out the
> rationale behind it. Anyways, here is what happened and maybe someone
> can throw some more light on what could have been the root cause of the
> problem.
>
> I uninstalled Eclipse and Java completely from my system.
> I then re-installed the latest version of Java (I had this same version
> previously too).
> But this time I installed it in the standard directory and not the
> custom directory that I was using before (Probably something here was
> wrong the first time).
> I then re-installed Eclipse (latest version again).
>
> And just like that, it all started working normally again, Debug mode
> and everything!
>
> What immediately comes to my mind is that the system environment
> variables could have got changed somehow. But I don't understand how
> this could have happened without me touching anything.
I'm sorry you had this trouble. I never run Eclipse on the JRE used by
the rest of my computer--always on a private one. Eclipse doesn't use
"system environment variables". It looks for the JRE in various, obvious
places. I always tell it where to look via the -vm option in eclipse.ini.
|
|
|
Powered by
FUDForum. Page generated in 0.02845 seconds