OneClick Tomcat won't startup due to

Document ID : KB000032837
Last Modified Date : 30/04/2019
Show Technical Document Details

OneClick Tomcat won't startup due to exception because default shutdown port, i.e. TCP/8005 was being used by other process. OneClick Tomcat log shows the following exception.

SEVERE: StandardServer.await: create[localhost:8005]: Address already in use: JVM_Bind
at Method)
at org.apache.catalina.core.StandardServer.await(
at org.apache.catalina.startup.Catalina.await(
at org.apache.catalina.startup.Catalina.start(
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(
at org.apache.catalina.startup.Bootstrap.start(
at org.apache.catalina.startup.Bootstrap.main(

Tomcat shutdown port, i.e. by default TCP/8005, has been used by other process. Because of that, OneClick Tomcat cannot allocate this port during start up. This happens typically when you install CABI on the same machine. When CABI Tomcat was running the default shutdown port TCP/8005 was being used so OneClick Tomcat won't be able to allocate the port.


We can reconfigure OneClick Tomcat to use different available TCP port, e.g. TCP/8006, for shutdown port. You can do the following steps.

1. Run the following netstat command to make sure that the TCP port you want to allocate is not being used. You should not get any entry as output of the command when the port is not being used.

On Windows:

netstat -aon | grep <port number>

On Linux/Solaris:

netstat -an | grep <port number>

Note: Replace <port number> with the new port number you want to use

2. Backup $SPECROOT/tomcat/conf/server.xml file and use vi editor or other text editor to modify


<Server port="8005" shutdown="SHUTDOWN">


<Server port="<new port number>" shutdown="SHUTDOWN">

Note: Replace <new port number> with the new port number you want to use

3. Restart OneClick Tomcat