There is no problem with the Eclipse normal run mode, but the debug mode does not start. ECLIPSE,MYECLIPSE,JDK doesn't solve the problem.
Later, the machine installed on the city of hot certification software shutdown, Debug mode can finally start normally.
It turns out that the city hotspot is conflicting with the JVM's debug mode.
Use Eclipse to debug Java code, both remote JVM and local JVM for socket communication. This error occurs because the socket is not communicating.
Urban hotspots are rather overbearing, and will not only modify Winsock, but also monitor and occupy some ports. Not just eclipse debug and it conflicts
A lot of software is limited.
Also for local debugging. The JVM creates a socket on the localhost and can ping the localhost at the command line to make sure the hosts are not tampered with.
You can also use the command at the command line netsh winsock reset reset winsock directory
After closing the city hotspots, not only is Java debug working, but remote debugging for Tomcat Server is OK. Finally found the root of the ills.
Reference: http://hi.baidu.com/yc_t/blog/item/c7f8eb95185c4643d1135e97.html