Topic
  • 4 replies
  • Latest Post - ‏2012-01-12T14:19:26Z by SystemAdmin
SystemAdmin
SystemAdmin
106 Posts

Pinned topic Worlight Server start issues

‏2012-01-11T02:48:10Z |
When i start the worklight server i get the following error below , however it says that the server started successfully.
And when i try to open console (http://localhost:8080/console) i get a 404.

Any pointers would be really helpful

SEVERE: Failed to initialize connector [Connectorhttp://HTTP/1.1-8080]
org.apache.catalina.LifecycleException: Failed to initialize component [Connecto
rhttp://HTTP/1.1-8080]
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)
at org.apache.catalina.core.StandardService.initInternal(StandardService
.java:559)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at org.apache.catalina.core.StandardServer.initInternal(StandardServer.j
ava:781)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at org.apache.catalina.startup.Catalina.load(Catalina.java:573)
at org.apache.catalina.startup.Catalina.load(Catalina.java:596)
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:281)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:449)
Caused by: org.apache.catalina.LifecycleException: Protocol handler initializati
on failed
at org.apache.catalina.connector.Connector.initInternal(Connector.java:9
11)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
... 12 more
Caused by: java.net.BindException: Address already in use: JVM_Bind /0.0.0.0:808
0
at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:386)
at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.jav
a:498)
at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:369)
at org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp
11JsseProtocol.java:119)
at org.apache.catalina.connector.Connector.initInternal(Connector.java:9
09)
... 13 more
Caused by: java.net.BindException: Address already in use: 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 org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(De
faultServerSocketFactory.java:54)
at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:376)
... 17 more
  • IdanAdar
    IdanAdar
    40 Posts

    Re: Worlight Server start issues

    ‏2012-01-11T07:24:23Z  
    Hello sri1230,

    In the pasted error message, I see the following:
    ... Caused by: java.net.BindException: Address already in use: JVM_Bind /0.0.0.0:808
    0
    This usually means that the port 8080 is already in use by another program.

    Worklight Server requires, by default, to use port 8080.
    • See if you can release this port for Worklight.

    • Alternatively it is possible to configure the server to use a different port.
    If you prefer this option (unless it is a must, I would advise to release port 8080 instead), there are two steps to do:

    1. In <path-to-server>/server/conf, edit the file worklight.properties
    1.1. Add the following:
    
    local.httpPort=put-an-available-port-value-here
    

    2. In <path-to-server>/tomcat/conf, edit the file server.xml
    2.1. Search for the string "Server port"
    2.2. Change the port value to a different one as well (not the same as the one put in worklight.properties)
  • SystemAdmin
    SystemAdmin
    106 Posts

    Re: Worlight Server start issues

    ‏2012-01-12T02:27:23Z  
    Thanks! that fixed the issue when i start the server. However when deploy a simple app from eclipse i get this.

    Failed deploying application to Worklight Server: Not Found; <HTML><HEAD><TITLE>404 Not Found</TITLE><BODY>

    Not Found

    </BODY></HTML>HTTP/1.1 400 Bad Request
    Server: Marimba Web Channel Manager

    It looks like its still trying to deploy to 8080, say if i changed the port to 9001, i cannot access localhost:9001
  • IdanAdar
    IdanAdar
    40 Posts

    Re: Worlight Server start issues

    ‏2012-01-12T05:40:15Z  
    I believe that would be because Worklight Studio, the Eclipse plug-in, is still configured to 8080 as well. I forgot. Apologies. :)

    In Eclipse, in the pane to the left, navigate to the application folder of your project, right-click it and from the Run As menu item choose Run Configurations. There, click on the Worklight Server configuration tab and finally, change the Server port value to match that of the server from the worklight.properties file.
  • SystemAdmin
    SystemAdmin
    106 Posts

    Re: Worlight Server start issues

    ‏2012-01-12T14:19:26Z  
    thanks that worked