- Plesk for Linux
- Plesk for Windows
Tomcat application is marked with an orange/yellow circle with an exclamation mark inside. When hovering over the exclamation mark, the following message is displayed:
CONFIG_TEXT: Actual status of the application does not correspond to the status retrieved from the database
Uploading a tomcat application to example.com in Domains > example.com > Java Applications fails with an error message:
PLESK_ERROR: Unable to start up Java application: Possible reason - Tomcat Java service is not currently running on the server.
Plesk can't reach the application for one of the following reasons:
- Tomcat service is not running on a server
- Tomcat service is not enabled for a domain
- Domain is not resolved to a Plesk IP
- Application is not packed into a valid .war package
- Incorrect code in the application itself
Warning: Support for Apache Tomcat is dropped in Plesk Onyx 17.8. In previous Plesk versions, it will be supported until reaching End-of-Life according to the Plesk Lifecycle Policy.
Depending on the cause, use the following solution:
- Start Tomcat service in Plesk > Tools and Settings > Services Management:
Enable Tomcat service for a domain in Domains > example.com > Java Applications > click Switch On
The domain should be properly resolved to correct Plesk IP address: IP address in Domains > example.com > Web Hosting Access should be the same as the IP resulted in pinging domain:
# ping example.com
PING example.com (203.0.113.2) 56(84) bytes of data.
64 bytes from 203.0.113.2: icmp_seq=1 ttl=57 time=176 ms
The application should be packed into a valid
The application cannot be loaded due to code in the application itself.
Additionally, reconfigure Tomcat for Plesk for Windows:
Connect to the server using RDP
Open Windows Command Prompt (CMD) in a Windows server: Right-click the Start charm, and then click Command Prompt (Admin).
Execute the following command:
C:\> "%plesk_dir%\\bin\\repair.exe" --reconfigure-tomcat
Check Tomcat logs in order to get more details about the issue: