Announcement Announcement Module
Collapse
No announcement yet.
Unrecognized Windows Sockets error: 0: JVM_Bind Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Unrecognized Windows Sockets error: 0: JVM_Bind

    Hi, I just downloaded STS version 2.2.0. Running on Windows 7.
    I am trying to run a web application on tc server.
    Getting a java.net.SocketException. My google search seemed to indicate that this may be due to another application using a port that tc server is trying to use but I am not sure how to find this information. Any help would be really appreciated.

    Nov 29, 2009 7:47:29 PM com.springsource.tcserver.security.PropertyDecoder <init>
    INFO: tcServer property decoder has been initialized.
    Nov 29, 2009 7:47:30 PM com.springsource.tcserver.serviceability.rmi.JmxSo cketListener init
    INFO: Started up JMX registry on 127.0.0.1:6969
    Nov 29, 2009 7:47:30 PM org.apache.coyote.http11.Http11Protocol init
    SEVERE: Error initializing endpoint
    java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
    at java.net.PlainSocketImpl.socketBind(Native Method)
    at java.net.PlainSocketImpl.bind(PlainSocketImpl.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.DefaultServerSocketFact ory.createSocket(DefaultServerSocketFactory.java:5 0)
    at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEnd point.java:521)
    at org.apache.coyote.http11.Http11Protocol.init(Http1 1Protocol.java:176)
    at org.apache.catalina.connector.Connector.initialize (Connector.java:1058)
    at org.apache.catalina.core.StandardService.initializ e(StandardService.java:677)
    at org.apache.catalina.core.StandardServer.initialize (StandardServer.java:795)
    at org.apache.catalina.startup.Catalina.load(Catalina .java:535)
    at org.apache.catalina.startup.Catalina.load(Catalina .java:559)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.apache.catalina.startup.Bootstrap.load(Bootstr ap.java:262)
    at org.apache.catalina.startup.Bootstrap.main(Bootstr ap.java:414)
    java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.apache.catalina.startup.Bootstrap.load(Bootstr ap.java:262)
    at org.apache.catalina.startup.Bootstrap.main(Bootstr ap.java:414)
    Caused by: java.lang.Error: LifecycleException: Protocol handler initialization failed: java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
    at org.apache.catalina.startup.Catalina.load(Catalina .java:538)
    at org.apache.catalina.startup.Catalina.load(Catalina .java:559)
    ... 6 more
    Caused by: LifecycleException: Protocol handler initialization failed: java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
    at org.apache.catalina.connector.Connector.initialize (Connector.java:1060)
    at org.apache.catalina.core.StandardService.initializ e(StandardService.java:677)
    at org.apache.catalina.core.StandardServer.initialize (StandardServer.java:795)
    at org.apache.catalina.startup.Catalina.load(Catalina .java:535)
    ... 7 more

  • #2
    The catalina.properties file in your tcserver instance directory (ie. c:\<testInstanceName>\conf\catalina.properties)

    should contain the list of configurable port numbers such as:

    ################################################
    ## ENTRIES BELOW ADDED AT INSTALL/CONFIGURE TIME
    ################################################

    tcserver.node=foo-c3e21
    shutdown.port=-1
    http.port=8080
    jmx.port=6969
    ajp.port=8009


    you can modify any of these ports, and restart your tc server instance, to see if that resolves the collision.

    _ellen

    Comment


    • #3
      Hi, thanks for taking the time to look into this for me. When trying to apply your suggested fix, I realized the real problem. I do not have write permissions to the tcserver install path, and the server needed to create start up files. When I modified the server path to use workspace metadata (Right-click on tcserver in server tab, select open, select workspace metadata radio button under server locations) problem was solved.

      Comment


      • #4
        Thanks for the update. I'll ping our doc team to make sure it's clearly documented.

        Comment

        Working...
        X