Tomcat starts an error unrecognized Windows Sockets error:0: Jvm_bind

 

Tomcat starts an error unrecognized Windows Sockets error:0: Jvm_bind resolution Today is very strange, when starting the tomact server side, often encountered this exception: Java.net.SocketException:Unrecognized Windows Sockets error:0: Jvm_bind At Java.net.PlainSocketImpl.socketBind (Native method) At Java.net.PlainSocketImpl.bind (Unknown Source) At Java.net.ServerSocket.bind (Unknown Source) At java.net.serversocket.<init> (Unknown Source) At java.net.serversocket.<init> (Unknown Source) At Org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket (defaultserversocketfactory.java:50) At Org.apache.tomcat.util.net.JIoEndpoint.init (jioendpoint.java:494) At Org.apache.coyote.http11.Http11Protocol.init (http11protocol.java:175) At Org.apache.catalina.connector.Connector.initialize (connector.java:1059) At Org.apache.catalina.core.StandardService.initialize (standardservice.java:578) At Org.apache.catalina.core.StandardServer.initialize (standardserver.java:792) At Org.apache.catalina.startup.Catalina.load (catalina.java:504) At Org.apache.catalina.startup.Catalina.load (catalina.java:524) At Sun.reflect.NativeMethodAccessorImpl.invoke0 (Native method) At Sun.reflect.NativeMethodAccessorImpl.invoke (Unknown Source) At Sun.reflect.DelegatingMethodAccessorImpl.invoke (Unknown Source) At Java.lang.reflect.Method.invoke (Unknown Source) At Org.apache.catalina.startup.Bootstrap.load (bootstrap.java:260) At Org.apache.catalina.startup.Bootstrap.main (bootstrap.java:412) Unrecognized Windows Sockets error:0: jvm_ Bind Workaround: First, the first judgment is not occupied: 1, the console input netstat-aon|findstr "8080" (red is a vertical bar OH), the following interface will appear: 2, this can be judged by the No. 4836 process in the listening. Second, to judge what software is taking up 3, then look at 4836 is what software, in the console input tasklist|findstr "6828", the following interface will appear: 4, see, is Javaw.exe. Finally solve the problem. 5. In Task Manager, the Javaw.exe process is closed. The problem is fixed. 

Loading in ...