• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Tomcat Issues After Update

C

Chris Pace

Guest
Recently, I upgraded Plesk on my server to Plesk 9.0. After installing, I was unable to launch any Tomcat applications, they would all throw a 404 error. After installing an update via the automatic update feature, this resolved THAT issue.

However, I have a new issue: Plesk is unable to start Tomcat via the GUI. I can start Tomcat manually, however.

In addition, newly installed Java applications don't work properly, unless I manually restart Tomcat.

It seems as if Plesk somehow "forgot" how to start/restart Tomcat. Any ideas on how to fix this?Recently, I upgraded Plesk on my server to Plesk 9.0. After installing, I was unable to launch any Tomcat applications, they would all throw a 404 error. After installing an update via the automatic update feature, this resolved THAT issue.

However, I have a new issue: Plesk is unable to start Tomcat via the GUI. I can start Tomcat manually, however.

In addition, newly installed Java applications don't work properly, unless I manually restart Tomcat.

It seems as if Plesk somehow "forgot" how to start/restart Tomcat. Any ideas on how to fix this?
 
Does anyone have an idea of where to start, to get this issue resolved? Thanks in advance!
 
Back
Top