Application Manager Fails to Start After Upgrade: Troubleshooting Tomcat Upgrade Issues
If Applications Manager fails to start after an upgrade, the issue may be related to an incomplete or failed Tomcat upgrade process.
This guide provides step-by-step instructions to help you identify the root cause and restore functionality.
Troubleshooting Steps
Check whether the Tomcat directories contain the required files. Navigate to the following paths under your Applications Manager installation directory:
ApplicationsManager/working/apache/tomcat/bin
ApplicationsManager/working/apache/tomcat/conf
ApplicationsManager/working/apache/tomcat/lib
The Tomcat upgrade rename process has failed if any folders are empty.
Resolution Steps
Follow the steps below to fix the Tomcat upgrade issue.
Step 1: Check for tomcat_9_new Folder
- Navigate to ApplicationsManager/working/apache/
- If a folder named tomcat_9_new exists, delete it.
Step 2: Rename the Existing Tomcat Folder
Rename the current Tomcat directory to include its version details before the upgrade.
For example:
ApplicationsManager/working/apache/tomcat → tomcat_old_9_16861
This helps preserve a backup of the previous version.
Step 3: Download and Extract the Correct Tomcat Version
Download the correct Tomcat ZIP file based on your Applications Manager (APM) version:
- From APM version 170000 to 172400 → tomcat_9_0_84
- From APM version 172500 to 176500 → tomcat_9_0_91
- From APM version 176600 and above → tomcat_0_106
After downloading:
- Extract the ZIP file.
- Copy the extracted Tomcat folder to ApplicationsManager/working/apache/
Step 4: Copy the Keystore File
If available, copy the appmanager.keystore file from the old Tomcat directory to the new one.
For example:
ApplicationsManager/working/apache/tomcat_old_9_16861/ → ApplicationsManager/working/apache/tomcat/
Step 5 (Optional): Update server.xml with Keystore and Truststore Paths
- Open the backup server.xml file located at ApplicationsManager/working/apache/tomcat_old_9_16861/conf/backup/server.xml
- Locate the <Connector> elements where SSLEnabled="true" is set.
- Note the keystoreFile and truststoreFile paths, if present.
- Copy these files to the corresponding location in the new Tomcat directory.
- Update the new Tomcat’s server.xml file accordingly.
For example: <Connector SSLEnabled="true"
URIEncoding="UTF-8"
port="SERVER_AGENT_PORT"
protocol="com.manageengine.appmanager.tomcatagent.http11.EncryptedHttp11NioProtocol"
keystoreFile="KEYSTORE_FILE"
sslEnabledProtocols="TLSv1.3+TLSv1.2"
useServerCipherSuitesOrder="true"/>Step 6 (Optional): Set Default TLS Ciphers
This step applies to:
- APM versions below 170000, and
- APM version 176600
To update ciphers:
- Open ApplicationsManager/working/apache/tomcat/conf/backup/server.xml
- Locate all <Connector> elements where SSLEnabled="true" is enabled.
- Replace the ciphers attribute with ciphers="TOMCAT_CIPHERS"
For example: <Connector SSLEnabled="true"
URIEncoding="UTF-8"
ciphers="TOMCAT_CIPHERS"
sslProtocol="TLS"
useServerCipherSuitesOrder="true"/>Note: Skip this step if you are using a custom cipher configuration.
Once all the steps have been completed, restart the Applications Manager service and verify that the product starts successfully without any errors.
New to ADSelfService Plus?
Related Articles
Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the below steps for troubleshooting. Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer this help ...Troubleshooting Applications Manager Plugin database migration failure after service pack upgrade of OPM and APM plugin
When upgrading OpManager from version 12.6.xxx to 12.7.xxx and updating the APM Plugin to 1651x, particularly when using Postgresql as the backend database, an essential one-time migration occurs. This migration involves moving our backend Postgresql ...Enabling JMX in Tomcat Application and adding JAVA Runtime / JMX Applications Monitor in Applications Manager
Configuring JMX for Apache Tomcat 1. On your Tomcat host, open the start menu and click on Tomcat Configuration (alternatively, edit the catalina.bat or catalina.sh file) 2. Click on the Java tab, then add the following Java Options: ...'Manager' application needs to be running in Tomcat server for Applications Manager to collect data from the Server. How can I enable the Manager application?
An application named Manager must be running in Tomcat Server Versions 5.x & above for Applications Manager to monitor the server. By default, this application will be running in the server. To check if it is already running, open the following url ...Tomcat Manager Application is running, but not accessible from Applications Manager
From tomcat v8 onwards, remote access to Manager Application is disabled by default. You can enable remote access by adding Applications Manager IP address in the RemoteAddrValve. Open the context.xml file located in ...