• 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 Issue Following Plesk 12 Upgrade

XSAH

New Pleskian
Our datacentre required us to upgrade from Plesk 9.5.4 to Plesk 12

After upgrading to Plesk version 12 all our Java web applications return Tomcat 404 error: "The requested resource is not available."

We are running Tomcat version: 5.5.23, this was not upgraded during the Plesk upgrade.

We are running Apache version: 2.2.3-91.el5, this was not upgraded during the Plesk upgrade.

We are running Java version: 1.6.0_35, this was not upgraded during the Plesk upgrade.

In catalina.out when Tomcat redeploys the war files I see:

May 30, 2015 2:53:05 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive fcbeta.war
May 30, 2015 2:53:05 PM org.apache.catalina.startup.ContextConfig init
SEVERE: Exception fixing docBase: {0}
java.net.MalformedURLException: no protocol: .jar:file:/usr/share/tomcat5/psa-webapps/fc.host.co.uk/fcbeta.war!/

The web application was working perfectly before the Plesk upgrade.

Does anyone have any ideas? Or can someone suggest where or what can be updated to change this location URL as it is not supplied in the war that I am deploying to Tomcat via Plesk?
 
Back
Top