After the Debian upgrade, the eclipse cannot be debugged, and the following prompts appear:
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:690]
FATAL ERROR in native method:jdwp No transports initialized,
Jvmtierror=agent_error_transport_init (197)
I switched to the JDK, I changed eclipse, and it's best to find an outdated Web page to know it's a Debian setup problem, Debian and Eclipse bug list, and the solution is as follows:
1.edit/etc/sysctl.d/bindv6only.conf and Net.ipv6.bindv6only 1 to 0.
2.sudo INVOKE-RC.D Procps Restart
Report:
Found the Reason/fix on this post:
http://www.eclipse.org/forums/index.php?t=msg&goto=505058& #msg_505058
The problem is caused by a pretty unbelievable thing introduced in
Debian. Found out that Java is no longer able to does any sort of
Network Connections anymore. Even connections to localhost failed ...
Someone decided to introduce a ipv6-only switch in netbase via
/etc/sysctl.d/bindv6only.conf. While this may or May is not a
Usefull default behaviour for the "the", the "is" Is this Java is
No longer able to do networking in all.
So to solve it your have to edit/etc/sysctl.d/bindv6only.conf and
Change the ' value of net.ipv6.bindv6only from ' 1 ' to ' 0 '. Then do a
"Sudo invoke-rc.d procps restart". After that, Java has networking
Again.