Unrecognized Windows Sockets error:0: Jvm_bind,intellij idea launches Tomcat exception

Source: Internet
Author: User

First use of IntelliJ idea, after configuring Tomcat, start the report below exception

Info: Command line argument: (x86) \java\servers\apache-tomcat-7.0. -\temp .-8-Ten  +: -: -org.apache.coyote.AbstractProtocol init info: Initializing Protocolhandler ["http-bio-8080"] .-8-Ten  +: -: -org.apache.coyote.AbstractProtocol init info: Initializing Protocolhandler ["ajp-bio-1099"] .-8-Ten  +: -: -org.apache.coyote.AbstractProtocol init critical: Failed to initialize end point associated with Protocolhandler ["ajp-bio-1099"]java.net.socketexception:unrecognized Windows Sockets Error:0: Jvm_bind at Java.net.PlainSocketImpl.socketBind (Native Method) at Java.net.PlainSocketImpl.bind (plainsocketimp L.java:365) at Java.net.ServerSocket.bind (Serversocket.java:319) at Java.net.ServerSocket.<init> (Serversocket.java:185) at Java.net.ServerSocket.<init> (Serversocket.java:141) at Org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket (Defaultserversocketfactory.java:  the) at Org.apache.tomcat.util.net.JIoEndpoint.bind (Jioendpoint.java: -) at Org.apache.tomcat.util.net.AbstractEndpoint.init (Abstractendpoint.java:715) at Org.apache.coyote.AbstractProtocol.init (Abstractprotocol.java:452) at Org.apache.catalina.connector.Connector.initInternal (Connector.java:978) at Org.apache.catalina.util.LifecycleBase.init (Lifecyclebase.java:102) at Org.apache.catalina.core.StandardService.initInternal (Standardservice.java:560) at Org.apache.catalina.util.LifecycleBase.init (Lifecyclebase.java:102) at Org.apache.catalina.core.StandardServer.initInternal (Standardserver.java:840) at Org.apache.catalina.util.LifecycleBase.init (Lifecyclebase.java:102) at Org.apache.catalina.startup.Catalina.load (Catalina.java:643) at Org.apache.catalina.startup.Catalina.load (Catalina.java:668) at Sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at Sun.reflect.NativeMethodAccessorImpl.invoke (Nativemethodaccessorimpl.java: the) at Sun.reflect.DelegatingMethodAccessorImpl.invoke (Delegatingmethodaccessorimpl.java: -) at Java.lang.reflect.Method.invoke (Method.java:597) at Org.apache.catalina.startup.Bootstrap.load (Bootstrap.java:253) at Org.apache.catalina.startup.Bootstrap.main (Bootstrap.java:427) .-8-Ten  +: -: -org.apache.catalina.core.StandardService initinternal Critical: Failed to initialize connector [CONNECTOR[AJP/1.3-1099]]org.apache.catalina.lifecycleexception:failed to initialize component [CONNECTOR[AJP/1.3-1099] at Org.apache.catalina.util.LifecycleBase.init (Lifecyclebase.java:107) at Org.apache.catalina.core.StandardService.initInternal (Standardservice.java:560) at Org.apache.catalina.util.LifecycleBase.init (Lifecyclebase.java:102) at Org.apache.catalina.core.StandardServer.initInternal (Standardserver.java:840) at Org.apache.catalina.util.LifecycleBase.init (Lifecyclebase.java:102) at Org.apache.catalina.startup.Catalina.load (Catalina.java:643) at Org.apache.catalina.startup.Catalina.load (Catalina.java:668) at Sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at Sun.reflect.NativeMethodAccessorImpl.invoke (Nativemethodaccessorimpl.java: the) at Sun.reflect.DelegatingMethodAccessorImpl.invoke (Delegatingmethodaccessorimpl.java: -) at Java.lang.reflect.Method.invoke (Method.java:597) at Org.apache.catalina.startup.Bootstrap.load (Bootstrap.java:253) at Org.apache.catalina.startup.Bootstrap.main (Bootstrap.java:427) caused By:org.apache.catalina.LifecycleException:Protocol handler initialization failed at Org.apache.catalina. Connector. Connector.initinternal (Connector.java:980) at Org.apache.catalina.util.LifecycleBase.init (Lifecyclebase.java:102)    ...  Amorecaused by:java.net.SocketException:Unrecognized Windows Sockets Error:0: Jvm_bind at Java.net.PlainSocketImpl.socketBind (Native Method) at Java.net.PlainSocketImpl.bind (plainsocketimp L.java:365) at Java.net.ServerSocket.bind (Serversocket.java:319) at Java.net.ServerSocket.<init> (Serversocket.java:185) at Java.net.ServerSocket.<init> (Serversocket.java:141) at Org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket (Defaultserversocketfactory.java:  the) at Org.apache.tomcat.util.net.JIoEndpoint.bind (Jioendpoint.java: -) at Org.apache.tomcat.util.net.AbstractEndpoint.init (Abstractendpoint.java:715) at Org.apache.coyote.AbstractProtocol.init (Abstractprotocol.java:452) at Org.apache.catalina.connector.Connector.initInternal (Connector.java:978)    ...  - More .-8-Ten  +: -: -Org.apache.catalina.startup.Catalina Load Info: initialization processedinch 455Ms .-8-Ten  +: -: -Org.apache.catalina.core.StandardService startinternal Info: Starting service Catalina .-8-Ten  +: -: -Org.apache.catalina.core.StandardEngine startinternal

is obviously a port conflict. But I do not have any other services locally, there will be no port occupancy.

Then check if the port is actually occupied,

At the start-run, enter CMD to open the command line interface, enter the command

Netstat-ano | Findstr "1099"

It is also found that there is no 1099 port occupancy situation.

Then has been Baidu check various solutions, most of the detection is how to deal with port conflicts:

One: Change the port number of the server;

Second: Close the process that occupies the current port

I also try to follow the solution provided by Baidu, look for the occupied port, modify the port, kill the process to wait, but no effect is reported this error.

At this point, I think it is not the other program port occupancy issues, should have a problem with Tomcat configuration.

There are two places that are configured with "1099". I tried to configure the port for larger data, or to report the same exception.

Finally suspected is two ports consistent, since the service time has been JMX1099 port, then in the AJP1099, then conflict.

Try to change one of them to "1098" and serve again, not to report this mistake.

This question tangled up in an afternoon, and finally settled. The whole settlement process was written out for the later few casing pits.

Unrecognized Windows Sockets error:0: Jvm_bind,intellij idea launches Tomcat exception

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.