Local Atom does not start, Failed starting local rpc webserver error

Document created by Adam Arrowsmith Employee on Jun 15, 2012
Version 1Show Document
  • View in full screen mode
When attempting to start a local Molecule or private Cloud node, the node does not start and the container log (located in ../<Atom root>/logs) contains the following error:

java.lang.IllegalStateException: Failed starting local rpc webserver
    at com.boomi.execution.forker.MultiProcessExecutionForker.start(MultiProcessExecutionForker.java:452)
    at com.boomi.container.cloudlet.execution.ClusterExecutionForker.start(ClusterExecutionForker.java:218)
    at com.boomi.execution.ExecutionManager.start(ExecutionManager.java:211)
    at com.boomi.container.cloudlet.Container.startServices(Container.java:231)
    at com.boomi.container.core.BaseContainer.start(BaseContainer.java:216)
    at com.boomi.container.core.BaseContainer.main(BaseContainer.java:966)
    at com.boomi.container.core.Container.main(Container.java:217)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.boomi.launcher.Launcher.main(Launcher.java:172)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)
    at com.install4j.runtime.Launcher.main(Unknown Source)
Caused by: java.net.BindException: Address already in use
    at sun.nio.ch.Net.bind(Native Method)
    at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:126)
    at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
    at sun.net.httpserver.ServerImpl.<init>(ServerImpl.java:68)
    at sun.net.httpserver.HttpServerImpl.<init>(HttpServerImpl.java:32)
    at sun.net.httpserver.DefaultHttpServerProvider.createHttpServer(DefaultHttpServerProvider.java:17)
    at com.sun.net.httpserver.HttpServer.create(HttpServer.java:111)
    at com.boomi.execution.forker.MultiProcessExecutionForker.start(MultiProcessExecutionForker.java:439)
    ... 17 more
This error is caused when two Molecule or Cloud nodes with forked execution enabled are started on the same server. When using forked execution (that is, each process execution runs in its own JVM), only one node may run on a given server. Forked execution is an optional setting for Molecule nodes but is always enabled for private Cloud nodes.

To resolve, identify a different server and start the second node service from that server

Attachments

    Outcomes