2.13.3.  Known Issues with this release

General Known Issues

JBPAPP-3789

Installing both Tomcat 5 and Tomcat 6 rpms causes Tomcat 5 to load the Tomcat 6 servlet JAR, tomcat6-servlet-2.5-api.jar, instead of geronimo-j2ee-1.4-apis.jar. Before Tomcat 6 is installed, Tomcat 5 uses:

/var/lib/tomcat5/common/lib/\[servlet\].jar -> /usr/share/java/servlet.jar -> 
/etc/alternatives/servlet -> /usr/share/java/geronimo-j2ee-1.4-apis.jar

Copy to Clipboard Toggle word wrap

After Tomcat 6 is installed, Tomcat 5 uses:

/var/lib/tomcat5/common/lib/\[servlet\].jar -> /usr/share/java/servlet.jar -> 
/etc/alternatives/servlet -> /usr/share/java/tomcat6-servlet-2.5-api.jar

Copy to Clipboard Toggle word wrap

There are two workarounds to this issue:

1. Install only the Tomcat 6 rpm, and install Tomcat 5 from the zip download.
2. Remove /var/lib/tomcat5/common/lib/\[servlet\].jar and copy geronimo-j2ee-1.4-apis.jar to /var/lib/tomcat5/common/lib/ to achieve the same effect.

JBPAPP-3762

When JBoss Enterprise Web Server is run on the IBM Java Development Kit 1.6 using Java Security Manager, Tomcat 6 does not start.

JBPAPP-3755

The current JBoss ON plugin (v2.3) for JBoss Enterprise Web Server is not supported on Windows or Solaris platforms, and there are several known issues on Red Hat Enterprise Linux. JBoss ON support for JBoss Enterprise Web Server on these platforms is planned for a future release of JBoss ON.

JBPAPP-3753

Undeploying any web application in the /manager and /admin applications causes an infinite loop. We do not currently recommend using the /manager or /admin applications to undeploy applications from your server.

JBPAPP-3735

The Apache HTTP Server module mod_ssl provides an interface to the OpenSSL library, which provides Strong Encryption using the Transport Layer Security/Secure Sockets Layer security protocols. To use this feature, install the mod_ssl package.

JBPAPP-3734

Unless <package>.noarch is specified for Tomcat 5 packages, yum fetches all Tomcat 5 packages from the Red Hat Enterprise Linux 5 base channel instead of the JBoss Enterprise Web Server channel. The installation instructions have been modified to include a work-around for this issue.

JBPAPP-3685

Attempting to edit server configuration details with the Tomcat 5 administration application results in some configuration information being lost from the configuration file (server.xml). At present we do not recommend using the the administration application for Tomcat 5.

JBPAPP-3658

Attempting to delete an existing host with the Tomcat 5 Administration Tool results in a NullPointerException. This is a problem upstream and is expected to be fixed for JBoss Enterprise Web Server 1.0.2.

JBPAPP-3646

The Tomcat 6 test suite attempts to compile and execute org.apache.catalina.tomcat.util.http.TestCookies instead of org.apache.tomcat.util.http.TestCookies. This is a problem upstream and is expected to be fixed for JBoss Enterprise Web Server 1.0.2.

JBPAPP-3644

Setting SECURITY_MANAGER="true" in sysconfig/tomcat5 or sysconfig/tomcat6 has no effect. To start the server securely, users must start with the -secure flag, like so:

catalina.sh start -secure

Copy to Clipboard Toggle word wrap

This is a problem upstream and is expected to be fixed for JBoss Enterprise Web Server 1.0.2.

JBPAPP-3628

When a virtual host is created using the /host-manager/html application, all actions work as expected, but the newly created host is not persistently added to the Tomcat configuration. Only the localhost is listed after server restart. This is a problem upstream and is expected to be fixed for JBoss Enterprise Web Server 1.0.2.

JBPAPP-3627

The Host Manager Help link in the /host-manager application leads to a HTTP 404 Error. This is a problem upstream and is expected to be fixed for JBoss Enterprise Web Server 1.0.2.

JBPAPP-3626

The links that Tomcat Web Application Manager displays for /host-manager and /manager result in a HTTP 404 Error. To work around this issue, add the following section to the WEB-INF/web.xml descriptor, immediately after the servlet-mapping section:

<welcome-file-list>
   <welcome-file>
      html/
   </welcome-file>
</welcome-file-list>

Copy to Clipboard Toggle word wrap

This is a problem upstream and is expected to be fixed for JBoss Enterprise Web Server 1.0.2.

JBPAPP-3625

When Tomcat Native is used upon server shutdown, a "Server accept failed" error occurs because the AJP Connector continues to wait for a client connection during shutdown. This is a problem upstream and is expected to be fixed for JBoss Enterprise Web Server 1.0.2.

JBPAPP-2852

RPM installation shares Java library files. When Enterprise Web Server coexists with Enterprise Application Platform or similar, library version conflicts occur. Only one version (either Enterprise Web Server or Enterprise Application Platform) can exist on one server when RPM installation is used. The workaround for this issue is to yum remove Enterprise Application Platform before installing Enterprise Web Server.

JBPAPP-2655

jaxp_parser_impl.jar and xml-commons-apis.jar are not included in Tomcat 6. This can cause a SAXParseException when parsing XML with a specific encoding (for example, GBK). Tomcat 6 requires JDK5 or higher; these JARs are not included in Tomcat because the JAXP implementation (JAXP 1.3) is built into JDK5. If users require encoding that is not supported by JAXP 1.3, the user must provide an external implementation of that encoding. The workaround for the missing JARs is therefore to copy them from Tomcat 5 into Tomcat 6.

JBPAPP-2150

The presence of a httpd-devel.i386 package in the Red Hat Enterprise Linux 5 base channel means that the httpd-devel may not be properly installed to the Red Hat Enterprise Linux x86_64 from the JBoss Enterprise Web Server channel. The correct way to install this package is to run the following command:

yum install httpd-devel.x86_64

Copy to Clipboard Toggle word wrap

JBPAPP-1966

Apache Tomcat handles SSL encryption and decryption such that browser-httpd communication takes place in HTTPS. However, communication between httpd and JBoss Enterprise Web Server takes place in plain HTTP. By default, redirects will also use HTTP. To use HTTPS redirects, define the following attributes on the JBoss HTTP Connector:

proxyName="www.somedomain.com" proxyPort="443" scheme="https"

Copy to Clipboard Toggle word wrap

If JBoss Enterprise Web Server handles redirect requests for both HTTP and HTTPS, you will need one HTTP connector per protocol.