Home/ Questions/Q 7599923
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-30T22:46:50+00:00

I am trying to debug a simple Java application on my machine using Eclipse

  • 0

I am trying to debug a simple Java application on my machine using Eclipse as an IDE. When I try to debug the application by entering the Debug Perspective, I set a breakpoint and start debug. Within a few seconds, the following pop-up window:

Launching unicodeRead has encountered a problem. Cannot connect to VM.

The message dumped on the console is as follows: 

ERROR: transport error 202: connect failed: Connection refused
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:708]
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)

How do I correct this? Why does this happen?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I just had the same problem.

    Yesterday everything worked fine, now nothing – same error as you gave. I found out that network admins made some changes in the meantime. Some firewall stuff. Problem is that Eclipse tries to establish connection to JVM at “localhost” (and some random port). When I tried pinging localhost (or 127.0.0.1) I got following:

    C:\Windows\system32>ping 127.0.0.1
Pinging 127.0.0.1 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.

    and

    C:\Windows\system32>ping localhost
Ping request could not find host localhost. Please check the name and try again.

    It seams that in some cases DNS is expected to resolve this, and if firewall prevents localhost requests to DNS – stuff breaks. I had to alter hosts file and remove comments in following lines, so I would not rely on DNS for this anymore:

    # 127.0.0.1       localhost
# ::1             localhost

    Although it is written that hosts file changes take effect immediately, I think that some processes locked this and restart was necessary in my case. After that, everything worked again.

    • 0