Troubleshooting: "The orb is not available" error when a toolkit server starts
When the Commerce+ Transaction Server toolkit and the Search toolkit run on the same machine,
the server that starts second might log an IllegalStateException stating
that the ORB is not available. You can safely ignore this error.
Problem
When you start the Commerce+ Transaction Servertoolkit, messages similar to the following appear in the server log:
E CWWKE0701E: bundle com.ibm.ws.management.j2ee.mejb:1.0.x (nnn)
[com.ibm.ws.management.j2ee.mejb.service.ManagementEJBService(104)] : The setServerStarted
method has thrown an exception java.lang.IllegalStateException:
com.ibm.ws.ejbcontainer.osgi.internal.EJBRuntimeException:
com.ibm.ws.exception.RuntimeError: java.lang.IllegalStateException: The orb is not available
at com.ibm.ws.ejbcontainer.osgi.internal.EJBContainerImpl.startSystemModule(EJBContainerImpl.java:236)
The same error can appear in the Search toolkit server log if the Commerce+ Transaction Server toolkit server starts first.
Cause
By default, the Object Request Broker (ORB) of each toolkit server listens on
port 2809. The server that starts first binds to this port.
When the second server starts, its ORB cannot bind to port
2809, and the mejb feature logs the error when
it tries to use the ORB.
Solution
Procedure
-
Optional: Confirm that another toolkit server is already listening on
port
2809.netstat -ano | findstr 2809Output similar to the following shows that a process is listening on the port:
TCP 127.0.0.1:2809 0.0.0.0:0 LISTENING 74024The last value is the process ID of the server that owns the port.
-
Ignore the error.
No functional impact has been observed. Both toolkit servers continue to start and run as expected.