There was a problem loading the comments.

Release Notes - Tomcat 5.5.x

Support Portal  »  Knowledgebase  »  Viewing Article

  Print

This Document will provide Tomcat 5 release notes for all operating systems offered by eApps. Please see the section specific to the operating system of your subscription. To get the operating system of your subscription take the steps below.

Log into your Control Panel > click My Account tab > Subscriptions > click the Name of the subscription (with type Virtuozzo Container)> the operating system is listed on the Server section of the page.


CentOS 5

The latest version available on Centos 5 plans is 5.5.30

Changes in 5.5.30
eApps notes
- none

Official Release Notes
- http://mirror.cloudera.com/apache/tomcat/tomcat-5/v5.5.30/RELEASE-NOTES


Changes in 5.5.29
eApps
- wrapper 3.3.9

Official Release Notes
- http://mirror.cloudera.com/apache/tomcat/tomcat-5/v5.5.29/RELEASE-NOTES

How to upgrade
-Log into your Control Panel > Click System Tab > All Applications > Tomcat-5 > Upgrade To Latest


Changes in 5.5.28
eApps
- catalina-manager.jr, commons-fileupload.jar and commons-io.jar were left out in previous version. This version fixes this issus.

Official Release Notes
- http://mirror.cloudera.com/apache/tomcat/tomcat-5/v5.5.28/RELEASE-NOTES

How to upgrade
- Log into your Control Panel > Click System Tab > All Applications > Tomcat-5 > Upgrade To Latest


Changes in 5.5.27
eApps
- catalina-manager.jr, commons-fileupload.jar and commons-io.jar were left out in previous version. This version fixes this issus.

Official Release Notes
- http://apache.oc1.mirrors.redwire.net/tomcat/tomcat-5/v5.5.27/RELEASE-NOTES

How to upgrade
- Log into your Control Panel > Click System Tab > All Applications > Tomcat-5 > Upgrade To Latest

CentOS 4 and Fedora
The latest version available on these hosting plans is 5.5.23.
To take advantage of the most current version, customers are encouraged to migrate to a CentOS 5 plan. For migration details please send a request to support@eapps.com.

UPGRADING:

From an Older Version of Tomcat 5.5.x - To upgrade from an older version of Tomcat 5.5.x, you can use the upgrade feature of the Control Panel.

  1. Login to your Control Panel and go to the System Tab

  2. Click on Upgrade Applications (if this is not present, you are already up to date).

  3. Select the latest version of Tomcat 5.5.x from the drop-down and click Upgrade

From an Older Version of Tomcat 5.0.x or Tomcat 4.x - To upgrade from an older version of Tomcat 5.0.x, or Tomcat 4, you must uninstall the old Tomcat and install the new Tomcat 5.5.x using the Control Panel.

  1. Login to your Control Panel and go to the System Tab

  2. Click on Alls Applications

  3. Select the version of Tomcat 5.0.x or Tomcat 4 and click Uninstall

  4. After the uninstall is completed, Click on Add Application and select Tomcat 5.5.x, then Install

NOTES

  • This version of Tomcat requires that you upgrade to J2SE (Java 5) or Java 6
  • The original /etc/tomcat5/tomcat.conf will be saved as /etc/tomcat5/tomcat.conf.rpmsave and a new one will be put in its place. If you have made any configuration changes, you will need to apply them again from the .rpmsave file. PLEASE do not just copy your old configuration file over, otherwise you will overlay important configuration settings!
  • Permissions will be updated to user:group tomcat:tomcat upon installation.
  • The ROOT webapp, server.xml, web.xml, context descriptor files, or any of their specific webapps, etc should not be overwritten if any changes were made. You should make a backup of /opt/tomcat5 before upgrading. If you want to re-apply any of the old files that that were backed up, you may rename the file (i.e. rename server.xml.rpmsave to server.xml).
  • Files that will be overwritten include the sample webapps, admin webapp, manager webapp, jar files that are included with tomcat, etc. This is not a comprehensive list, but a guide to what you need to look for when problems arise.
  • JSP Development Mode now set to False - For performance reasons, the JSP Development Mode is now set to False. This means that JSP pages will not be automatically be used when changed. You would have to clear out the Work Directory and Restart Tomcat, or delete the compiled JSP, to pick up the changes. You can also change the setting back to TRUE. Please see the tomcat user guide at http://support.eapps.com/hsp/tomcat for more information.


Share via
Did you find this article useful?  

Related Articles


On-Premise Help Desk Software by SupportPal

Categories

© Cloudscale365