Release Notes - Tomcat 6
- 24/04/2007 9:15 PM
This Document will provide Tomcat 6 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 6.0.32
Changes in 6.0.32
eApps Release Notes
- None
Official Release Notes
- http://download.nextag.com/apache/tomcat/tomcat-6/v6.0.32/RELEASE-NOTES
Changes in 6.0.29
eApps Release Notes
- None
Official Release Notes
- http://download.nextag.com/apache/tomcat/tomcat-6/v6.0.29/RELEASE-NOTES
Changes in 6.0.26
eApps Release Notes
- None
Official Release Notes
- http://download.nextag.com/apache/tomcat/tomcat-6/v6.0.26/RELEASE-NOTES
eApps Release Notes
- None
Official Release Notes
- http://download.nextag.com/apache/tomcat/tomcat-6/v6.0.32/RELEASE-NOTES
Changes in 6.0.29
eApps Release Notes
- None
Official Release Notes
- http://download.nextag.com/apache/tomcat/tomcat-6/v6.0.29/RELEASE-NOTES
Changes in 6.0.26
eApps Release Notes
- None
Official Release Notes
- http://download.nextag.com/apache/tomcat/tomcat-6/v6.0.26/RELEASE-NOTES
Changes in 6.0.24
eApps Release Notes
- None
Official Release Notes
- http://download.nextag.com/apache/tomcat/tomcat-6/v6.0.24/RELEASE-NOTESChanges in 6.0.20
eApps Release Notes
- None
Official Release Notes
- http://download.nextag.com/apache/tomcat/tomcat-6/v6.0.20/RELEASE-NOTES
Changes in 6.0.18
eApps Release Notes
- upgraded Java Service Wrapper from verion 3.2.3 to version 3.3.1
Official Release Notes
- http://download.nextag.com/apache/tomcat/tomcat-6/v6.0.18/RELEASE-NOTES
How To Upgrade
As good practice it is always recommend that you make a backup before upgrading. You can make a full system backup using the server side backup feature from your control panel if you have purchased some backup space. Another option will be to make a copy of your Web applicaitons and configurations in the /opt/tomcat6/config directory.
- Log into your Control Panel > click System Tab > All Applications > Tomcat 6 > Upgrade To Latest
CentOS 4
The latest version availabl on CentOS 4 plans is 6.0.14. 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.
Changes in 6.0.14
eApps Specific Notes
- None
Officail Release Notes
- http://download.nextag.com/apache/tomcat/tomcat-6/v6.0.14/RELEASE-NOTES
How To Upgrade
From an Older Version of Tomcat 6 - To upgrade from an older version of Tomcat 6.x, you can use the upgrade feature of the Control Panel.
From Version 4 or Version 5 - To upgrade to Tomcat 6 from a previous version 4 or version 5 of Tomcat, you will need to uninstall the previous version first. First, backup the /etc/tomcat#/tomcat.conf configuration file. If you have made any configuration changes, you will need to apply them again from this backup to the new Tomcat. PLEASE do not just copy your old configuration file over, otherwise you will overlay important configuration settings!
The old /opt/tomcat# directory will be preserved, as well as the ROOT webapp, server.xml, web.xml, context descriptor files, or any of their specific webapps. It is highly recommended that you make a backup of /opt/tomcat# 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) or copy the pertinent information to the new 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 recompiled when changed. You would have to clear our 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.
Changes in 6.0.18
eApps Release Notes
- upgraded Java Service Wrapper from verion 3.2.3 to version 3.3.1
Official Release Notes
- http://download.nextag.com/apache/tomcat/tomcat-6/v6.0.18/RELEASE-NOTES
How To Upgrade
As good practice it is always recommend that you make a backup before upgrading. You can make a full system backup using the server side backup feature from your control panel if you have purchased some backup space. Another option will be to make a copy of your Web applicaitons and configurations in the /opt/tomcat6/config directory.
- Log into your Control Panel > click System Tab > All Applications > Tomcat 6 > Upgrade To Latest
CentOS 4
The latest version availabl on CentOS 4 plans is 6.0.14. 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.
Changes in 6.0.14
eApps Specific Notes
- None
Officail Release Notes
- http://download.nextag.com/apache/tomcat/tomcat-6/v6.0.14/RELEASE-NOTES
How To Upgrade
From an Older Version of Tomcat 6 - To upgrade from an older version of Tomcat 6.x, you can use the upgrade feature of the Control Panel.
-
Login to your Control Panel and go to the System Tab
-
Click on Upgrade Applications (if this is not present, you are already up to date).
-
Select the latest version of Tomcat 6 from the drop-down and click Upgrade
From Version 4 or Version 5 - To upgrade to Tomcat 6 from a previous version 4 or version 5 of Tomcat, you will need to uninstall the previous version first. First, backup the /etc/tomcat#/tomcat.conf configuration file. If you have made any configuration changes, you will need to apply them again from this backup to the new Tomcat. PLEASE do not just copy your old configuration file over, otherwise you will overlay important configuration settings!
The old /opt/tomcat# directory will be preserved, as well as the ROOT webapp, server.xml, web.xml, context descriptor files, or any of their specific webapps. It is highly recommended that you make a backup of /opt/tomcat# 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) or copy the pertinent information to the new 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 recompiled when changed. You would have to clear our 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.