Jaspersoft Tomcat service fails to start with errors in catalina.out

Products

• Clarity PPM On Premise

Issue/Introduction

Jaspersoft Tomcat service fails to start and advanced reporting standalone URL not accessible 

Catalina.out:

failed to initialize component [Connector[HTTP/1.1-8080]]

SEVERE [main] org.apache.catalina.util.LifecycleBase.handleSubClassException Failed to initialize component [Connector[HTTP/1.1-8080]]

        org.apache.catalina.LifecycleException: Protocol handler initialization failed

Caused by: java.net.BindException: Address already in use

                at java.base/sun.nio.ch.Net.bind0(Native Method)

                at java.base/sun.nio.ch.Net.bind(Net.java:455)

                at java.base/sun.nio.ch.Net.bind(Net.java:447)

                at java.base/sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:227)

                at java.base/sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:80)

                at org.apache.tomcat.util.net.NioEndpoint.initServerSocket(NioEndpoint.java:228)

                at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:211)

                at org.apache.tomcat.util.net.AbstractEndpoint.bindWithCleanup(AbstractEndpoint.java:1141)

                at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:1154)

                at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:581)

                at org.apache.coyote.http11.AbstractHttp11Protocol.init

Environment

Clarity 16.01 and Jaspersoft 7.8 

Cause

Tomcat ports are occupied by another process (8080, 8005, 8009)

Resolution

Tomcat ports are occupied by another process (8080, 8005, 8009) and the orphaned PIDs for tomcat relates to the port conflict where the port are not closed completely after shutting tomcat down.

When running a "netstat -an | grep 8080" the output showed port established even after shutting down tomcat service and killing threads (PS - ef | grep tomcat and kill - 9 PIDs) 

The source of the other PIDs was from other older jaspersoft Tomcat homes on the server where the service was also started. Removed all tomcat homes and kept only the 7.8 Jaspersoft Tomcat active.