• 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 breaks after upgrade

C

cuppett

Guest
My working web applications stopped working after upgrade. I don't know if mod_jk got upgraded or not, but for some reason the ifmodule mod_jk.so doesn't work anymore. Commenting out the ifmodule seems to make the jk try to go to Tomcat.

Then, once it's there, it appears that the webapps aren't there. I get 404 errors.

A re-install of Tomcat altogether doesn't work to resolve stuff either.

You would think that totally removing all *tomcat* RPMs and mod_jk and then re-installing them would get it back; however, if you blow away the /var/tomcat4 directory, there isn't enough information consolidated in the tomcat only RPMs to ensure that Plesk is even able to talk to tomcat again. And the psa-* directories won't even get recreated under /var/tomcat4.

This support has always been flaky, but now it just won't work... period.
 
Back
Top