The following article describes various AvailabilityGuard Apache Tomcat errors and how they can be resolved -
Important Note: Tomcat errors will impact the AvailabilityGuard system availability, and can be identified by reviewing Tomcat log files.
Tomcatuser is disabled / removed
By default Apache Tomcat service is configured to run under the local tomcatuser account. If the tomcatuser account is disabled or removed, Tomcat will fail to start. To resolve this error, use the Local System account for the Tomcat service or use a domain account with local administrator rights.
Incorrect java path
Apache Tomcat relies on Java. When the path to the jvm.dll is incorrect, Tomcat will fail to start. This error may occur for example when java is updated on the AvailabilityGuard master server.
To review of update the jvm.dll path, open file explorer on the master server and navigate to %CATALINA_HOME%\bin. Double click on the tomcatw.exe file (alternatively click on Configure Tomcat from the Start Menu). Select the Java tab and review or update the value in the Java Virtual Machine text box – as illustrated below.
Insufficient memory allocated for Tomcat
The “java.lang.OutOfMemoryError: Java heap space” error in the AvailabilityGuard rg log files indicates tomcat is not configured with sufficient memory. To allocate additional memory, open the Tomcat configuration window as described above and increase the Maximum memory pool value.