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

How Plesk should handle tomcat and Java applications?

A

AISPL

Guest
Please update your reviews all java users

I find bit frustating to use plesk for Java Applications.

1. We have big applications, (800+ jsps, 500+beans, &65 controllers)
We all the time have to upload War files, even there is small problem in one jsp, whole lot have to be uploaded

2. We can not have any logging folder for our own log4j logging, which we do on other server in the Webbapplication root folder.

There are similar isuues in deploying servlets,sturts etc.
Also is frustating to see ':9080' in URL.

So why not plesk allow JSP files in httpdoc, the class files in WEB-Inf folder , that is standard deployment.

Please do add your views ALL JAVA USERS
 
After struggling for seven days with poor plesk documentation on java hosting, we surrenderred and got ENSIM license. Roll out is next few hours.
Plesk , you have good product except practical java hosting.
 
Back
Top