Chapter 8.  Known Issues with this release

General Known Issues

JBPAPP-6655

When Java is installed on Red Hat Enterprise Linux from RPM, the alternatives system determines which Java is used by default. A user will not normally have the JAVA_HOME environment variable set, and Java continues to work, but trying to use JSVC without JAVA_HOME set results in a Cannot Locate Java Home error. The workaround for this issue is to set JAVA_HOME manually, or use the -java-home option.

JBPAPP-6592

Deploying an application as a Tomcat 6 user with "tomcat, manager, admin" roles leads to a 403 error.

JBPAPP-6326

WAITFORREMOVE is not configurable, which means that there is a ten second delay when a node failsover to another node.

JBPAPP-6297

When using Tomcat 6, changing the default for loadMetricCapacity, loadHistory and loadDecayFactor throws a NullPointerException. To workaround this issue, use the default configuration for these classes.

JBPAPP-6197

Using the Tomcat shutdown procedure /usr/sbin/tomcat6 or Red Hat Enterprise Linux 6 fails when JON is being used to manage a tomcat instance installed via RPMs.

JBPAPP-6133

Tomcat5 cannot start if the security manager is enabled.

JBPAPP-6128

JON does not discover Tomcat 5 and 6 on Windows so it cannot be used to monitor them.

JBPAPP-6096

The JON httpd plugin cannot discover httpd if /etc/httpd does not exist. This issue only occurs when Enterprise Web Server is installed via ZIP, and the workaround is to manually create /etc/httpd for Red Hat Enterprise Linux and Solaris, and C:\apache for Windows.

JBPAPP-4882

manager.xml cannot be installed when adding a virtual host through the host-manager on tomcat6.

JBPAPP-4873

Running tomcat 5 on Red Hat Enterprise Linux with security manager enabled fails to start with the default catalina.policy.

JBPAPP-4265

There is an issue with ldap:// with STARTTLS, which causes the server to respond with error code 500. The logs show that this is a user testuser authentication failed error.

JBPAPP-3900

The libraries provided by Tomcat 5 and 6 differ between the RPM and ZIP distributions. Refer to the JIRA for further details.

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-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-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.

JBPAPP-3627

The Host Manager Help link in the /host-manager application leads to a HTTP 404 Error.

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

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.

JBPAPP-3614

Due to a race condition caused by a bug in mod_proxy, a 503 error may be returned when a node is killed, instead of failing over to another node.

JBPAPP-2955

Tomcat error pages incorrectly identify the brew build.

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.

Hibernate Known Issues

JBPAPP-5898

When scrolling a query that has a join fetch on a collection, only the first item in the collection is correctly loaded. The workaround for this issue is to remove the fetch join on the collection, but it does result in n+1 selects.

mod_cluster Known Issues

JBPAPP-6257

Sessions are sticky by default with Tomcat, so the Nodes do not failover. See HTTP Load Balancing Connector Guide for information on enabling failover.