Issued:

2013-11-20

Updated:

2013-11-20

RHBA-2013:1721 - tomcat6 bug fix update

Synopsis

tomcat6 bug fix update

Type/Severity

Bug Fix Advisory

Topic

Updated tomcat6 packages that fix several bugs are now available for Red Hat Enterprise Linux 6.

Description

Apache Tomcat is a servlet container for the Java Servlet and JavaServer Pages (JSP) technologies.

This update fixes the following bugs:

• Previously, an attempt to build the tomcat6-docs-webapp package failed when Red Hat Enterprise Linux was running on IBM System z or 64-bit IBM POWER Series computers. With this update, no architecture is set in the build target and the package can be built as expected. (BZ#845786)

• When a user, whose name did not correspond to any existing group name, was specified in the /etc/sysconfig/tomcat6 file, the Tomcat web server failed to start. This update applies a patch to fix this bug and Tomcat no longer fails in the described scenario. (BZ#915447)

• Due to a bug in the checkpidfile() function, an attempt to execute the "service tomcat6 status" command failed and an error message was returned. The underlying source code has been modified to fix this bug and the command now works properly. (BZ#950647)

• Due to a bug in the checkpidfile() function, the status script did not return the correct PID. This bug has been fixed and the status script now returns the correct PID as expected. (BZ#960255)

• The Tomcat web server included a version of the tomcat-juli.jar file that was hard coded to use classes from the java.util.logging package instead of the log4j framework. Consequently, Tomcat could not be configured to use log4j unless the complete version of the tomcat-juli.jar and tomcat-juli-adapters.jar files had been downloaded. With this update, the tomcat6 packages now contain the correct versions of these files to configure log4j. (BZ#977685)

• When multiple tomcat instances were configured as described in the /etc/sysconfig/tomcat6 configuration file and the instance name was different from the name of the tomcat directory, the "service status" command failed. With this update, the underlying source code has been modified to fix this bug and the command no longer fails in the described scenario. (BZ#989527)

Users of tomcat6 are advised to upgrade to these updated packages, which fix these bugs.

Solution

Before applying this update, make sure all previously released errata relevant to your system have been applied.

This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258

Affected Products

Updated Packages

• tomcat6-docs-webapp-6.0.24-62.el6.noarch.rpm
• tomcat6-lib-6.0.24-62.el6.noarch.rpm
• tomcat6-servlet-2.5-api-6.0.24-62.el6.noarch.rpm
• tomcat6-admin-webapps-6.0.24-62.el6.noarch.rpm
• tomcat6-6.0.24-62.el6.src.rpm
• tomcat6-jsp-2.1-api-6.0.24-62.el6.noarch.rpm
• tomcat6-el-2.1-api-6.0.24-62.el6.noarch.rpm
• tomcat6-6.0.24-62.el6.noarch.rpm
• tomcat6-javadoc-6.0.24-62.el6.noarch.rpm
• tomcat6-webapps-6.0.24-62.el6.noarch.rpm

Fixes

• This content is not included.BZ - 845786
• This content is not included.BZ - 915447
• This content is not included.BZ - 950647
• This content is not included.BZ - 960255
• This content is not included.BZ - 977685
• This content is not included.BZ - 989527

CVEs

(none)

References

(none)

Additional information

• The Red Hat security contact is This content is not included.secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.
• Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.