• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Upgrade to tomcat6?

T

threads

Guest
Has anyone had any experience of trying to upgrade from Plesks tomcat5 to tomcat6?

One of my clients has a requirement to have tomcat6 installed and I am struggling :-(
 
I did manage to get things running but not reliably. Due to other problems (persistent reboots) with the server I moved to UK2NET and started from scratch with a clean Ubuntu machine. Installing tomcat6 was then straight forward when it did not have to know about Plesk etc.
 
You must log in or register to reply here.

Similar threads

D
Question IMAP default folders (Sent/Drafts/Trash) stay in English after mailbox creation – how do you solve this long-term?
Replies
5
Views
5K
dbmtrde
D
Azurel
Input AlmaLinux8to9 upgrade leaves Plesk in broken state with insufficient service checks and recovery guidance
Replies
2
Views
2K
Azurel
Azurel
burnley
Question granular scope permissions for Plesk REST API
Replies
2
Views
773
burnley
burnley
K
Resolved Watchdog says Plesk Web Server down since 18.0.79
Replies
3
Views
1K
King555
K
danami
Resolved Plesk PHP packages built with older libavif which breaks yum updates
Replies
1
Views
1K
Martin Dias
Martin Dias
Back
Top