原文地址 :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)
我換來jdk,換了eclipse 還是出錯,最好上網查到一個過期的網頁才知道是debian設置的問題,debian 及eclipse的bug list都有,解決方法如下:
1.edit /etc/sysctl.d/bindv6only.conf and net.ipv6.bindv6only行的1改成0
2.sudo invoke-rc.d procps restart
附:
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 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 not be a
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.ipv6.bindv6only from "1" to "0". Then do a
"sudo invoke-rc.d procps restart". After that, java has networking
again.