Tomcat stops immediately after starting from service manager
search cancel

Tomcat stops immediately after starting from service manager


Article ID: 191700


Updated On:


CA Automic Workload Automation - Automation Engine


When attempting to start tomcat from the service manager (smgr), it will stop immediately.  The following can be seen in the service manager logs:

20200527/125158.634 - U00022019 Client statement: process 'Tomcat' should be started.
20200527/125158.634 - U00022031 Client data: User 'domain\user' of computer 'computer name'.
20200527/125158.634 - U00022004 Starting process 'Tomcat' ...
20200527/125158.634 - U00022005 ... with command line  'C:\Automic\Automation.Platform\ServiceManager\bin\..\..\..\External.Resources\apache-tomcat-9.0.19\bin\launcher.exe "start.bat > ..\logs\console.log 2<&1" "stop.bat"'.
20200527/125158.634 - U00022006 ... and start directory  'C:\Automic\Automation.Platform\ServiceManager\bin\..\..\..\External.Resources\apache-tomcat-9.0.19\bin'.
20200527/125158.640 - U00022007 Process 'Tomcat' (ID '45392') successfully started.
20200527/125158.649 -          Window: Hnd=05e7005a, Title='launcher'
20200527/125158.772 - U00022012 Process 'Tomcat' (ID '45392') ended.
20200527/125158.772 - U00022022 Process 'Tomcat' ended, exit code='1'.

There are no messages in the console.log that tomcat writes to.

This occurs when:
Service manager is used to start and stop tomcat (something that is usually done if the ONE Installer was used to install AWA)
At some point before attempting to start tomcat via smgr, it was stopped with smgr 
This does not happen every time, but some of the time


Release : 12.3



This is caused because even though the direct process that the smgr starts, "Launcher.exe", is stopped when tomcat is stopped from the smgr, the java process that is started from Launcher.exe does not stop.  This causes a new process to be unable to start.


Find the PID for the java process that has a command like:
"C:\Program Files\Java\jdk1.8.0_201\bin\java.exe" -Djava.util.logging.config.file="C:\Automic\External Resources\apache-tomcat-9\conf\" -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager "-Djdk.tls.ephemeralHDKeySize=2048" -Djava.protocol.handlre.pkgs=org.apache.catalina.webresources -Xmx2048m -Dignore.endorsed.dirs="" -classpath "C:\Automic\External Resources\apache-tomcat-9.0.19\bin\boostrap.jar;C:\Automic\Automation\External Resources\apache-tomcat-9.0.19\bin\tomcat-juli.jar" -Dcatalina.base="C:\Automic\External.Resources\apache-tomcat-9.0.19" -Dcatalina.home="C:\Automic\External.Resources\apache-tomcat-9.0.19""C:\Automic\External Resources\apache-tomcat-9.0.19\temp" org.apache.catalina.startup.Bootstrap start

And kill that process either from the Task Manager or command line