Address: http://blog.csdn.net/sxhong/archive/2010/01/09/5166693.aspx
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)
In exchange for JDK, I still had errors when I changed eclipse. I 'd better find an expired webpage online to know that it was a problem with Debian settings. Debian
And eclipse bug list. The solution is as follows:
1. Change edit/etc/sysctl. d/bindv6only. conf and net. ipv6.bindv6only to 0.
2. sudo invoke-rc.d procps restart
Appendix:
Found the reason/fix on this post:
Http://www.eclipse.org/forums/index.php? T = MSG & goto = 505058 & # msg_505058
The problem was caused by a pretty unbelievable thing introduced in
Debian. Found out that Java was no longer able to do any sort
Network Connections anymore. Even connections to localhost
Failed...
Someone decided to introduce a ipv6-only switch in netbase
/Etc/sysctl. d/bindv6only. conf. While this may or may not be
Usefull default behaviour for the general the result is that Java
Is
No longer able to do networking at all.
So to solve it you have to edit/etc/sysctl. d/bindv6only. conf and
Change the value of net. Release 6.bindv6only from "1" to "0". Then do
"Sudo invoke-rc.d procps restart". After that, Java has networking
Again.