• 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.

Ugly Bug in Tomcat Addon of Plesk

Chris_Becker

New Pleskian
Hi, I realized, there is a reproducible bug in the Tomcat Addon.

When you deploy a Java-Application in a container "sample.war" you will be able to access the corresponding application under http://theurl.tld/sample

But I want to be able to access the Java-Application under http://theurld.tld/

In case of a Tomcat server you need to rename the War-file to "ROOT.war". The bug is, that Plesk maps the application to http://theurl.tld/ROOT because obviously the special but most important case of "ROOT" has no special handling. And under http://theurl.tld/ROOT you get a tomcat error message, because tomcat deployed the ROOT.war correctly.

In my opinion this is a really critical bug, and it is really easy to fix.

I would be really thankful to close the bug very recent, because without it I (and everybody else) has almost no possibility to use the tomcat addon, because almost EVERY customer want to deploy the java app as a ROOT-App.

Official documentation for the special case of ROOT.war can be found at: http://tomcat.apache.org/tomcat-7.0-doc/virtual-hosting-howto.html#General
 
Back
Top