• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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