Release Notes 1.0.2

JBoss Hibernate

JBoss Hibernate is an implementation of the Java Persistence 1.0 identifier and is an Object/Relational Mapping solution for Java environments.

JBoss Enterprise Web Server consists of Hibernate Core 3.3.2.GA_CP04, Hibernate Annotations 3.4.0.GA_CP04, and Hibernate Entity Manager 3.4.0.GA_CP04.

mod_cluster

JBoss mod_cluster 1.0.10.GA_CP01 is an httpd-based load balancer. Like mod_jk, it uses a communication channel to forward requests from HTTPD to an application server node.

Red Hat Enterprise Linux 6

JBoss Enterprise Web Server 1.0.2 introduces support for Red Hat Enterprise Linux 6.

Support for Online Certificate Security Protocol

Apache httpd 2.2 contains support for Online Certificate Security Protocl (OCSP).

General Fixed Issues

JBPAPP-4529

No request is forwarded to a worker node after it has failed, even though it is marked as available in the balance manager. This issue has been resolved with JBoss Enterprise Web Platform 1.0.2.

JBPAPP-4207

Running service5.bat remove on Windows disables the Tomcat service instead of removing it. This has been fixed JBoss Enterprise Web Server 1.0.2.

JBPAPP-3938

The manager application is unable to undeploy a .war application deployed on the Tomcat 5 server. Deploying an expanded .war throws a similar error but does undeploy the application. This issue is fixed with this release of JBoss Enterprise Web Server.

JBPAPP-3888

apachectl22 executes /usr/sbin/httpd instead of /usr/sbin/httpd22, which causes the wrong httpd version to run. This issue has been fixed and apachectl22 now runs /usr/sbin/httpd22.

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

This issue has been fixed by correcting the symlinks in tomcat5 so that it links to the servlet and jsp jars from the tomcat5 build instead of the alternatives one.

JBPAPP-3758

Configuration for the welcome page of Enterprise Web Server in httpd/conf.d/welcome redirects requests to /error/noindex.html file, but the noindex.html file in the httpd/www/error directory does not exist. Zips installed on Red Hat Enterprise Linux 5 do not work, as a result. This issue has been fixed with JBoss Enterprise Web Server 1.0.2.

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-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). This issue has been fixed with JBoss Enterprise Web Server 1.0.2.

JBPAPP-3658

Attempting to delete an existing host with the Tomcat 5 Administration Tool results in a NullPointerException. This has been fixed with 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 issue is fixed upstream and with this release of JBoss Enterprise Web Server.

JBPAPP-3644

Setting SECURITY_MANAGER="true" in sysconfig/tomcat5 or sysconfig/tomcat6 has no effect. This issue has been resolved by modifying catalina.sh to switch to -security mode if SECURITY_MANAGER=true is set.

mod_cluster Fixed Issues

JBPAPP-3349

Should you encounter an [emerg] create_mem_node <node file path> failed error, use the ipcrm -m command before restarting httpd.

Security Fixed Issues

CVE-2011-0419

It was found that the apr_fnmatch() function used an unconstrained recursion when processing patterns with the '*' wildcard. An attacker could use this flaw to cause an application using this function, which also accepted untrusted input as a pattern for matching (such as an httpd server using the mod_autoindex module), to exhaust all stack memory or use an excessive amount of CPU time when performing matching.

CVE-2011-0013

A cross-site scripting (XSS) flaw was found in the Manager application. A malicious web application could use this flaw to conduct an XSS attack, leading to arbitrary web script execution with the privileges of victims who are logged into and viewing Manager application web pages.

CVE-2010-4172

A cross-site scripting (XSS) flaw was found in the Manager application, used for managing web applications on Apache Tomcat. If a remote attacker could trick a user who is logged into the Manager application into visiting a specially-crafted URL, the attacker could perform Manager application tasks with the privileges of the logged in user.

CVE-2010-3718

It was found that web applications could modify the location of the Apache Tomcat host's work directory. As web applications deployed on Tomcat have read and write access to this directory, a malicious web application could use this flaw to trick Tomcat into giving it read and write access to an arbitrary directory on the file system.

CVE-2010-2068

A flaw was discovered in the way the mod_proxy_http module of the Apache HTTP Server handled the timeouts of requests forwarded by a reverse proxy to the back-end server. In some configurations, the proxy could return a response intended for another user under certain timeout conditions, possibly leading to information disclosure. Note: This issue only affected httpd running on the Windows operating system.

CVE-2010-1623

It was found that certain input could cause the apr-util library to allocate more memory than intended in the apr_brigade_split_line() function. An attacker able to provide input in small chunks to an application using the apr-util library (such as httpd) could possibly use this flaw to trigger high memory consumption.

CVE-2010-1452

A flaw was found in the way the mod_dav module of the Apache HTTP Server handled certain requests. If a remote attacker were to send a carefully crafted request to the server, it could cause the httpd child process to crash.

CVE-2010-1157

A possible minor information leak was found in the way Apache Tomcat generated HTTP BASIC and DIGEST authentication requests. For configurations where a realm name was not specified and Tomcat was accessed via a proxy, the default generated realm contained the hostname and port used by the proxy to send requests to the Tomcat server.

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.