Tomcat in the debug mode to start the direct prompt: The box can not be started, no error message, but the direct start, there will be an error message

Run the project today, debug mode start Tomcat, direct bullet box: Unable to start (translation, because later finishing, so all forget the then)

Later try to start directly, found not to play box, but console has reported error messages.

Similar to the following error

2015-8-13 17:29:03 Org.apache.tomcat.util.net.jioendpoint$acceptor Run
Critical: Socket Accept Failed
Java.net.SocketException:select failed
At Java.net.PlainSocketImpl.socketAccept (Native Method)
At Java.net.PlainSocketImpl.accept (plainsocketimpl.java:390)
At Java.net.ServerSocket.implAccept (serversocket.java:453)
At Java.net.ServerSocket.accept (serversocket.java:421)
At Org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket (defaultserversocketfactory.java:61)
At Org.apache.tomcat.util.net.jioendpoint$acceptor.run (jioendpoint.java:365)
At Java.lang.Thread.run (thread.java:619)

This online a meal to find AH!!! Before checking that the Tomcat port is not occupied, it is not found. Whether Tomcat is not itself a problem, re-installed Tomcat, the result is still an error.

Method One, look at your machine installed not installed Thunderbolt Online Accelerator, Tomcat and Thunderbolt Online accelerator has conflict (what conflict to ask Thunder, online said it seems to be destroying the TCP/IP protocol), I put my thunder online accelerator unloading, in the start Tomcat does not explode above the error. ---others to test.

Method Two, "You can try the Netsh winsock reset command, enter the cmd input netsh winsock reset and then reboot, I have already been able to run"--online said this practice is also feasible, but I did not try, if you use this method can solve the problem, please leave a message below , convenient for other people. --my own test, it works.

Method Three, is to add additional startup parameters:-djava.net.preferipv4stack=true, such as: This method I tried to start Tomcat is not let the console burst error, but in the Address bar access: http://localhost:8080/, The browser is loaded and does not display the Tomcat home page. Cup is used at once to reach 100%.

Nothing in the real effect.

Tomcat in the debug mode to start the direct prompt: The box can not be started, no error message, but the direct start, there will be an error message