Red Hat JBoss Web Server 1.0

Release Notes 1.0.1

for use with Red Hat JBoss Web Server 1.0.1Edition 1.0.1

Last Updated: 2017-10-19

Red Hat JBoss Web Server 1.0 Release Notes 1.0.1

for use with Red Hat JBoss Web Server 1.0.1Edition 1.0.1

Laura Baileylbailey@redhat.com

Legal Notice

Copyright © 2010 Red Hat, Inc.

This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0Unported License. If you distribute this document, or a modified version of it, you must provideattribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hattrademarks must be removed.

Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert,Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.

Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinitylogo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and othercountries.

Linux ® is the registered trademark of Linus Torvalds in the United States and other countries.

Java ® is a registered trademark of Oracle and/or its affiliates.

XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United Statesand/or other countries.

MySQL ® is a registered trademark of MySQL AB in the United States, the European Union andother countries.

Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally related toor endorsed by the official Joyent Node.js open source or commercial project.

The OpenStack ® Word Mark and OpenStack logo are either registered trademarks/service marksor trademarks/service marks of the OpenStack Foundation, in the United States and other countriesand are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed orsponsored by the OpenStack Foundation, or the OpenStack community.

All other trademarks are the property of their respective owners.

Abstract

These release notes contain important information related to Red Hat JBoss Web Server 1.0.1. Youshould read these Release Notes in their entirety before installing Red Hat JBoss Web Server 1.0.1.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents

1. INTRODUCTION1.1. Overview

2. INSTALLATION NOTES2.1. Installation Notes for Red Hat Enterprise Linux2.2. Red Hat Enterprise Linux directory structure2.3. Running the Installation

2.3.1. Running a RPM Installation2.3.2. Running a ZIP Installation

2.4. Installation Notes for Microsoft Windows2.4.1. Prerequisites2.4.2. Installing Enterprise Web Server2.4.3. Installing services

2.4.3.1. Service security settings2.5. Windows directory structure2.6. Installation Notes for the Solaris Operating System

2.6.1. Installation using the Solaris package2.6.2. Installation using the zip package

2.7. The Solaris operating system directory structure2.8. Running on a Solaris Operating System Installation2.9. Uninstalling the package in the Solaris operating sytem2.10. Source Files2.11. Excluded, Removed and Deprecated Items

2.11.1. Excluded Items2.11.2. Deprecated Items2.11.3. Removed Items

2.12. Product Support and License Website Links2.13. Issues fixed in this release

2.13.1. Fixed Security Issues2.13.2. General Fixed Issues2.13.3. Known Issues with this release

A. REVISION HISTORY

22

335557

10101111131314141616171919202020202021212424

28

Table of Contents

1

1. INTRODUCTION

These release notes contain important information related to JBoss Enterprise Web Server 1.0.1. Newfeatures, known problems, resources, and other current issues are addressed here.

1.1. Overview

JBoss Enterprise Web Server is a fully integrated and certified set of components for hosting Java webapplications. It is comprised of the industry's leading Web Server (Apache HTTP Server), the popularApache Tomcat Servlet container as well as the mod_jk connector and the Tomcat Native library. Thisrelease of the JBoss Enterprise Web Server consists of the following components:

Apache Tomcat 5.5.28: Apache Tomcat is an implementation of the Java Servlet andJavaServer Pages technologies. The Java Servlet and JavaServer Pages specifications aredeveloped by Sun under the Java Community Process. Apache Tomcat version 5.5 implementsthe Servlet 2.4 and JavaServer Pages 2.0 specifications.

NOTE

The default Red Hat Enterprise Linux 5 installation contains Apache Tomcat5.5.23.

Apache Tomcat 6.0.24: Apache Tomcat is an implementation of the Java Servlet andJavaServer Pages technologies. The Java Servlet and JavaServer Pages specifications aredeveloped by Sun under the Java Community Process. Apache Tomcat version 6.0 implementsthe Servlet 2.5 and JavaServer Pages 2.1 specifications.

Apache Tomcat Native 1.1.19: Tomcat can use the Apache Portable Runtime to providesuperior scalability, performance, and better integration with native server technologies. TheApache Portable Runtime is a highly portable library that is at the heart of Apache HTTP Server2.x. APR has many uses, including access to advanced IO functionality (such as sendfile, epolland OpenSSL), OS level functionality (random number generation, system status, etc), andnative process handling (shared memory, NT pipes and Unix sockets). This package containsthe Tomcat native library which provides support for using APR in Tomcat.

Apache Tomcat Connector (mod_jk) 1.2.28: Apache Tomcat Connector (mod_jk) is abridge between Apache Httpd and Apache Tomcat using binary AJP protocol. It also contains aload balancer, which provides clustering and fault tolerance.

Apache HTTP Server 2.2.14: The Apache HTTP Server Project is an effort to develop andmaintain an open-source HTTP server for modern operating systems. The goal of this project isto provide a secure, efficient and extensible server that provides HTTP services in sync with thecurrent HTTP standards.

NOTE

The default Red Hat Enterprise Linux 5 installation contains Apache HTTP Server2.2.3-31.

Release Notes 1.0.1

2

This release of JBoss Enterprise Web Server is certified for the following Operating Systems :

Red Hat Enterprise Linux 4, latest update (x86, x86_64)

Red Hat Enterprise Linux 5, latest update (x86, x86_64)

Solaris 9 (x86, SPARC32, SPARC64)

Solaris 10 (x86, x86_64, SPARC64)

Windows Server 2003 SP2 (x86, x86_64)

Windows Server 2008 R2 (x86, x86_64)

IMPORTANT

Red Hat products, including Red Hat Enterprise Linux, are signed with a Red Hat Key toindicate that these packages and JARs are shipped by Red Hat. Red Hat Signed JARsmean you can be confident that your product distribution is exactly the distribution thatwas shipped by Red Hat.

2. INSTALLATION NOTES

This section contains information related to installing JBoss Enterprise Web Server version 1.0.1,including hardware and platform requirements and prerequisites.

IMPORTANT

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

2.1. Installation Notes for Red Hat Enterprise Linux

The preferred method for installing the JBoss Enterprise Web Server on Red Hat Enterprise Linux is byusing the Red Hat Enterprise Linux rpm file; however we will also discuss installation via the zippackage.

You must have adequate disk space to install JBoss Enterprise Web Server while also allowing enoughspace for your applications.

A working, supported installation of Java 1.6 on your system will also be necessary. On Red HatEnterprise Linux 4 systems subscribed to the Extras channel, this can be achieved by executing:

Where <version> is 1.6.0 and <vendor> can be sun or ibm.

On Red Hat Enterprise Linux 5 systems, this can be achieved by executing:

up2date java-<version>-<vendor>

yum install java-<version>-<vendor>

2. INSTALLATION NOTES

3

Where <version> is 1.6.0 and <vendor> can be sun, ibm or openjdk. Please note that OpenJDK isonly available for version 1.6.0.

Once the Java SDK has been installed, please check to make sure the desired JDK is chosen byexecuting the following:

If the JDK in use is not the desired option, the above commands can be used to switch to another JDK.

IMPORTANT

By switching alternatives for the Java JDK for Tomcat, other software that makes use ofthe java and javac commands will now be using the same JDK as well.

JBoss Enterprise Web Server can either be installed via the Red Hat Network (RHN) or the JBossCustomer Support Portal (CSP).

Installing via RHN

1. If you are subscribed to the Red Hat Application Stack channel, you will need to disablethat channel before installing the JBoss Enterprise Web Server.

2. Subscribe to the JBoss Enterprise Web Server channel: Red Hat Enterprise Linux 4 ews or RedHat Enterprise Linux 5 ews

The available channels for Red Hat Enterprise Linux 4 are:

jb-ews-1-i386-es-4-rpm

jb-ews-1-x86_64-as-4-rpm

jb-ews-1-i386-es-4-rpm

jb-ews-x86_64-es-4-rpm

The avaliable channels for Red Hat Enterprise Linux 5 are:

jb-ews-1-i386-server-5-rpm

jb-ews-1-x86_64-server-5-rpm

3. Install the packages: tomcat5, tomcat6, tomcat-native, httpd22 and mod_jk

On Red Hat Enterprise Linux 4 to install the packages, execute:

4. On Red Hat Enterprise Linux 5, to install the Tomcat 5 packages, you must make the followingmodification to the /etc/yum.conf file. Comment out the option:

exactarch=1

alternatives --config javaalternatives --config javac

up2date tomcat6 tomcat6-webapps tomcat6-admin-webapps tomcat5 tomcat5-webapps tomcat5-admin-webapps ecj tomcat-native httpd22 mod_jk-ap20

Release Notes 1.0.1

4

NOTE

This change should be reverted when installation is complete to return yumconfiguration to the default settings.

Then install the packages:

Installing via CSP

1. Download the JBoss Enterprise Web Server zip file from the CSP site that is correct for youroperating system and architecture.

2. Unzip the file.

IMPORTANT

You can install both Tomcat 5 and Tomcat 6 in parallel on your system, however portaddresses would need to be modified in order to avoid conflict.

2.2. Red Hat Enterprise Linux directory structure

The following is the default directory layout after a successful installation:

.|-- jboss-ews-1.0 |-- httpd (includes mod_jk) |-- tomcat5 (includes tomcat-native) |-- tomcat6 (includes tomcat-native) |-- doc|-- jboss-ews-1.0-src |-- httpd |-- mod_jk |-- tomcat5 |-- tomcat6 |-- tomcat-native

2.3. Running the Installation

To run the downloaded packages differs depending on the download method. This section will now detailhow to run the installation for a RHN download and CSP download.

2.3.1. Running a RPM Installation

Running Tomcat version 5 or 6

Tomcat can be started, stopped, and configured to start automatically at boot time either from thecommand line or using a graphical tool.

yum install tomcat6 tomcat6-webapps tomcat6-admin-webapps tomcat5.noarch tomcat5-webapps.noarch tomcat5-admin-webapps.noarch tomcat-native httpd mod_jk-ap20

2. INSTALLATION NOTES

5

The tomcat5 or tomcat6 services can be started and stopped using the service command as root ona console window (as is typical of a network service):

Starting and stopping the tomcat5 service:

Starting and stopping the tomcat6 service:

Once the tomcat service has been started, you can verify that it is running by pointing your web browserto http://localhost:8080.

The tomcat service runs under a new tomcat system user. Due to file system permissions it may benecessary to use the su -s /bin/bash tomcat system command to deploy the application under thewebapps directory. Alternatively, a developer can be listed in the tomcat user group by the systemadministrator. The best approach is to use the Web Console (URL above) to deploy the application.

The behavior at boot can be controlled with the chkconfig command (see the chkconfig man pagefor further details).

Configuration can then be altered in the /etc/sysconfig/tomcat5 file for Tomcat version 5 and the /etc/sysconfig/tomcat6 file for Tomcat version 6.

Running the HTTP Server

The HTTP Server can be started, stopped, and configured to start automatically at boot time either fromthe command line or using a graphical tool.

The following examples of running the HTTP Server will also cover the differences of undertaking this onRed Hat Enterprise Linux 4 and 5

You can start and stop the HTTP Server service using the service command as root on a consolewindow (as is typical of a network service):

Starting and stopping the HTTP Server service on Red Hat Enterprise Linux 4:

Starting and stopping the HTTP Server service on Red Hat Enterprise Linux 5:

service tomcat5 start

service tomcat5 stop

service tomcat6 start

service tomcat6 stop

service httpd22 start

service httpd22 stop

service httpd start

service httpd stop

Release Notes 1.0.1

6

Configuration can then be altered in the /etc/sysconfig/httpd22 file on Red Hat EnterpriseLinux 4 and the /etc/sysconfig/httpd file on Red Hat Enterprise Linux 5.

Running the mod_jk

To load the mod_jk module, the file /etc/httpd22/conf/httpd.conf on Red Hat Enterprise Linux 4or the file /etc/httpd/conf/httpd.conf on Red Hat Enterprise Linux 5 needs to be updated, and a workers.properties file needs to be added in that directory. See /usr/share/doc/mod_jk-ap20-1.2.28/mod_jk.conf.sample and /usr/share/doc/mod_jk-ap20-1.2.28/workers.properties.sample for examples of how this can be achieved.

Running log4j for logging in Tomcat 6

To use log4j for logging in Tomcat 6, install the tomcat6-log4j rpm file.

Running log4j for logging in Tomcat 5

To use log4j for logging in Tomcat 5, you must copy the appropriate files from the Tomcat 6 distributionincluded in JBoss Enterprise Application Platform 1.0.1. Copy log4j.jar from tomcat6/extras into tomcat5/common/lib. Copy log4j.properties from tomcat6/extras files into tomcat5/common/classes.

Running Apache Tomcat Native

Edit /etc/sysconfig/tomcat5 file for Tomcat 5 or /etc/sysconfig/tomcat6 for Tomcat 6 andadd the LD_LIBRARY_PATH variable so that it points to the library correct library:

The correct value when running on 64bit architecture is:

The correct value when running on 32bit architecture is:

2.3.2. Running a ZIP Installation

Running Tomcat version 5 or 6

After extracting the zip file, check to see if a user called tomcat exists on the system by running thefollowing command:

If the user does not exist then it will need to be added, along with the appropriate usergroup. In order toachieve this, execute the following:

Once this is completed, if the tomcat user will be running Tomcat, then the ownership of the tomcatdirectories will need to be changed to reflect this:

For Tomcat 5:

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib64/

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/

id tomcat

groupadd -g 91 -r tomcatuseradd -c "Tomcat" -u 91 -g tomcat -s /bin/sh -r -d /home/tomcat tomcat

chown -R tomcat:tomcat tomcat5

2. INSTALLATION NOTES

7

For Tomcat 6:

To test that the above commands have been successful, check that the tomcat user has executionpermission to the tomcat install path.

The JAVA_HOME variable must now be set and this can be achieved by either modifying your .bashrcfile or by modifying the Tomcat catalina.sh file.

If you chose to modify your .bashrc file, add the following line with the correct path to suit your systemsconfiguration (a path is provided here as an example only):

If you chose to modify your tomcat5/bin/catalina.sh or tomcat6/bin/catalina.sh file(depending on the version of Tomcat installed), add the following line with the correct path to suit yoursystems configuration (a path is provided here as an example only):

To start and stop Tomcat, execute the follwing scripts as the user tomcat:

To start Tomcat:

To stop Tomcat:

Once the Tomcat service has been started, you can verify that it is running by pointing your web browserto http://localhost:8080.

Running the HTTP Server

In order to run the HTTP Server, the distcache and pcre rpm packages must be installed as they are arequirement of mod_ssl. To check if these dependencies are already installed, execute the following ina command prompt:

The output will either say the rpms are not installed or it will display the package name followed by theversion number. If distcache or pcre is not installed, execute:

for Red Hat Enterprise Linux 4:

For Red Hat Enterprise Linux 5:

chown -R tomcat:tomcat tomcat6

export JAVA_HOME=/usr/lib/jvm/java

JAVA_HOME=/usr/lib/jvm/java

sh startup.sh

sh shutdown.sh

rpm -q distcache pcre

up2date distcacheup2date pcre

Release Notes 1.0.1

8

While undertaking the install, you will be asked it you wish to proceed. When this occurs press the y key.

Once installation is complete run the following command in order to check that the package was installedsuccessfully.

If the package was successfully installed then the output of the command will be the package name andthe version number.

Now, after you have extracted the Enterprise Web Server zip file, change into the httpd directory andrun the post install script by executing the following:

Check to see if a user called apache exists on the system by running the following command:

If the user does not exist then it will need to be added, along with the appropriate usergroup. In order toachieve this, execute the following:

Once this is completed, if the apache user will be running the httpd service, then the ownership of theHTTP directories will need to be changed to reflect this:

To test that the above commands have been successful, check that the apache user has executionpermission to the HTTP server install path.

Start the HTTP server by changing to the httpd directory and executing:

Stop the HTTP server by executing:

Running the mod_jk

To load the mod_jk module, the file httpd/conf/httpd.conf needs to be updated, and a workers.properties file needs to be added in that directory. See doc/mod_jk/mod_jk.conf.sample and doc/mod_jk//workers.properties.sample forexamples of how this can be achieved.

yum install distcacheyum install pcre

rpm -q distcacherpm -q pcre

./.postinstall

id apache

groupadd -g 91 -r apache 2> /dev/null || :useradd -c "Apache" -u 91 -g apache -s /bin/sh -r -d /home/apache apache 2> /dev/null || :

chown -R apache:apache httpd

su -m -c "./sbin/apachectl start"

su -m -c "./sbin/apachectl stop"

2. INSTALLATION NOTES

9

Running Apache Tomcat Native

The native library for Tomcat 6 is setup to be used by default, with the LD_LIBRARY_PATH and -Djava.library.path having been set accordingly within the catalina.sh file.

For Tomcat 6, start the service and check that you see a message similar to:

Feb 8, 2008 12:27:41 PM org.apache.catalina.core.?AprLifecycleListener initINFO: Loaded APR based Apache Tomcat Native library 1.x.y.Feb 8, 2008 12:27:41 PM org.apache.catalina.core.?AprLifecycleListener initINFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].Feb 8, 2008 12:27:41 PM org.apache.coyote.http11.?Http11AprProtocol initINFO: Initializing Coyote HTTP/1.1 on http-8080

For Tomcat 5, start the service and if the tomcat native library is not used, a message similar to the onebelow will appear:

INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path

Running log4j for logging in a zip installation of Tomcat 6

In order to use log4j logging in Tomcat 6, copy the content of the extras/ directory into the lib/directory and restart Tomcat.

2.4. Installation Notes for Microsoft Windows

Read this section to learn how to install JBoss Enterprise Web Server on a Microsoft Windows system.

2.4.1. Prerequisites

There are a number of prerequisites that must be fulfilled before you can install JBoss Enterprise WebServer on Microsoft Windows.

1. Java SDK 1.6

2. System environment variables:

JAVA_HOME

The install location of Java SDK 1.6.

TMP

Temporary directory.

TEMP

Temporary directory.

You must use a local administrator account to set up a system environment variable.

Release Notes 1.0.1

10

Go to Control Panel > System and click on the Advanced tab. Click the Environment Variables button. Click the New for System Variables, and enter the required JAVA_HOME, TMP and TEMP name-value pairs.

2.4.2. Installing Enterprise Web Server

1. Download the JBoss Enterprise Web Server zip file from the CSP site that is correct for youroperating system and architecture.

2. Unzip the Enterprise Web Server binary inside C:\Program Files.

To extract the .zip archive, right-click on the file and select Extract All.... Click Next.When prompted for the extract location, click Browse and navigate to the C:\Program Filesdirectory. Click Finish.

Your files will be extracted to C:\Program Files\Red Hat\Enterprise Web Server.

3. Run JBoss Enterprise Web Server as an administrator:

1. Run the Command Prompt as an administrator. Click on Start > All Programs > Accessories. Right-click on Command Prompt and select Run as administrator.

NOTE

You will need to select Run as administrator even if you are logged inas an administrator.

NOTE

Windows Server 2003 does not have the User Account Control concept, soyou will only need to run the Command Prompt (cmd.exe).

2. Inside the Command Prompt, type the following to move to the etc directory of yourEnterprise Web Server installation:

3. Run the post-installation script by typing:

This script creates the required symbolic links (Junction Points) for temporary logging andconfiguration directories.

2.4.3. Installing services

Installing Apache Httpd as a service

1. Run the Command Prompt as administrator. Click on Start > All Programs > Accessories. Right-click on Command Prompt and select Run as administrator.

2. Move to the bin directory of your new installation:

C:\> cd /D "C:\Program Files\Red Hat\Enterprise Web Server\etc"

C:\> call postinstall.bat

2. INSTALLATION NOTES

11

Then type the following:

NOTE

This step can cause a Firewall security dialog prompt to allow networking accessfor the Apache Httpd service. Click Allow if you wish to access this service fromthe network.

NOTE

By default, Apache Httpd is configured to listen on port 80. If you have MicrosoftIIS installed, ensure either that:

World Wide Web... service is stopped and the Startup Type is set to Manual

World Wide Web... service is configured to listen on a different port

Alternatively, you can edit the httpd.conf file before installing the service andchange the Listen directive to a port that will not collide with the InternetInformation Service listening ports.

Installing Apache Tomcat as a service

1. Run the Command Prompt as administrator. Click on Start > All Programs > Accessories. Right-click on Command Prompt and select Run as administrator.

NOTE

On 64-bit Windows, you need to use the 64-bit version of the Command Prompt(cmd.exe). Running the cmd command from a 32-bit application launches a 32-bit Command Prompt instance. This causes the service setup script to fail with aFile Not Found warning.

2. Move to the sbin directory in your JBoss Enterprise Web Server installation:

Then type the following to install Apache Tomcat 6:

You can check the service parameters by typing tomcat6w.exe.

C:\> cd /D "C:\Program Files\Red Hat\Enterprise Web Server\bin"

C:\> httpd -k install

C:\> cd /D "C:\Program Files\Red Hat\Enterprise Web Server\sbin"

C:\> call service6.bat install

Release Notes 1.0.1

12

NOTE

You can install Apache Tomcat 5.5 instead with the call service5.bat install command, and check its service parameters with tomcat5w.exe.

2.4.3.1. Service security settings

Follow the steps in this section to ensure that the account used to run the services has full control overthe C:\Program Files\Red Hat folder and all of its subfolders.

For Windows Server 2003:

1. Right-click on the C:\Program Files\Red Hat folder and click on Properties.

2. Select the Security tab.

3. Click the Add.. button and type in LOCAL SERVICE.

4. Check the Full Control check box for the new LOCAL SERVICE account.

5. Click the Advanced button.

6. Inside the Advanced Security Settings for Red Hat dialog, check the Replace permissions on all child objects... check box and click the OK button.

The new settings will be applied after a short while (one or two minutes).

This procedure differs slightly in Windows Server 2008 or Windows Server 2008R2, but the end resultmust be the same.

2.5. Windows directory structure

The following is the default directory layout after a successful installation:

|-- bin|-- doc|-- etc| |-- httpd| |-- postinstall.bat| |-- ssl| `-- sysconfig|-- include|-- lib64|-- sbin|-- share| |-- apache-tomcat-5.5.28| |-- apache-tomcat-6.0.24| |-- java| |-- tomcat5| `-- tomcat6`-- var |-- cache |-- log |-- run `-- www

2. INSTALLATION NOTES

13

The Windows directory structure follows Red Hat Enterprise Linux conventions:

The bin and sbin directories contain the executable files for Apache HTTP Server and Tomcat.

The etc directory contains configuration files for Apache HTTP Server and the post-installationscript.

The share directory contains Apache Tomcat 5 and 6 installations and shared Java JARs.

The var contains two sub-directories:

log

This directory contains the log files for Apache HTTP Server and Tomcat.

www

Apache HTTP Server looks in this directory for web content in the default configuration.

2.6. Installation Notes for the Solaris Operating System

The preferred method for installing the JBoss Enterprise Web Server on the Solaris operating system isby using the provided Solaris package file; however we will also discuss installation via the zippackage.

Download the desired Enterprise Web Server package that you wish to use and that will match yourSolaris version and CPU architecture.

NOTE

For Solaris you can choose between i386 (x86) and x86_64 system versions. If running ax86_64 JVM choose the x86_64 version of the Enterprise Web Server.

If you are building the packages from source, the Tomcat 5 and Tomcat 6 packages (regardless of theTomcat you choose) will be built by using the srpms.

2.6.1. Installation using the Solaris package

Log into your system as root and use the gunzip and pkgadd commands. The commands will be:

and

The output will be:

The following packages are available:1 RHATews JBoss Enterprise Web Server (i386) 1.0.0,REV=2.el5

gunzip RHATews-1.0.0*-solaris10-i386.package.gz

pkgadd -d RHATews-1.0.0*-solaris10-i386.package

Release Notes 1.0.1

14

Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]:

Type 1 or just press enter. The following information will now appear:

JBoss Enterprise Web Server(i386) 1.0.0,REV=2.GA END USER LICENSE AGREEMENTJBOSS(r) ENTERPRISE MIDDLEWARE(tm) The end user license agreement ("EULA") governs the use of the various software modules that collectively comprise JBoss Enterprise Middlewareand any related updates, source code, appearance, structure and organization,regardless of the delivery mechanism. The JBoss Enterprise Middleware EULA can be found here:http://www.redhat.com/licenses/jboss_eula.html ## Executing checkinstall script.Using </opt> as the package base directory.## Processing package information.## Processing system information.## Verifying disk space requirements.## Checking for conflicts with packages already installed.## Checking for setuid/setgid programs.

This package contains scripts which will be executed with super-userpermission during the process of installing this package.

Do you want to continue with the installation of <RHATews> [y,n,?]

The package installer contains custom scripts that execute during install and are used for setting up theapache and tomcat user accounts. When package installer asks whether you wish to continue with theinstallation type y and press enter.

Installation will then commence and the following will be displayed:

## Executing postinstall script.Apache group (id=48) already exists. +++ or created if notApache user (id=48) already exists.Generating private RSA key ... OKGenerating new (+++ user hostname displayed here) certificate ... OKTomcat group (id=91) already exists.Tomcat user (id=91) already exists. -----------------------------------------------------------------------NOTICE----------------------------------------------------------------------- JAVA_HOME environment variable is not set.

2. INSTALLATION NOTES

15

Either set the JAVA_HOME or edit the configurationscripts inside `/opt/redhat/ews/etc/sysconfig' directoryand set the JAVA_HOME to the installed JDK location. Installation of <RHATews> was successful.

After the installation finishes the package is installed within the /opt/redhat/ews directory.

The package information can be checked by executing the following command:

NOTE

During installation the system generated a notice that the JAVA_HOME environmentvariable was not set. Configuring this is discussed later in the Section 2.8, “Running on aSolaris Operating System Installation” section.

2.6.2. Installation using the zip package

Installing the zip package requires root access and the GNU version of tar.

The package should be uncompressed inside the /opt directory since the post installation script will notrun if installation occurs within a different location.

The commands to achieve this are as follows:

Once extraction of the archive has completed, the post install script must be run in order to setup theuser accounts and final directories with required access privileges.

This is achieved with the following commands:

Once the post install process has been completed, the users and groups apache with an ID of 48 and tomcat with an ID of 91, will have been created. The apache user will be used to run httpd, while the tomcat user will be used to run tomcat.

In addition, the post install process will also create the following additional directories that the tomcatgroup has write permission to:

/var/logs/tomcat5

/var/logs/tomcat6

2.7. The Solaris operating system directory structure

The following is the default directory layout after a successful installation:

pkginfo -l RHATews

cd /optunzip -q RHATews-1.0.0*-solaris10-i386.zip

cd /opt/redhat/ews/etcsh .postinstall

Release Notes 1.0.1

16

.|-- /opt/redhat/ews |-- bin |-- doc |-- etc |-- lib |-- lib64 (present only for the x86_64 systems platform) |-- include |-- README |-- man |-- share |-- tomcat5 |-- tomcat6 |-- sbin |-- var

The Solaris operating system directory structure is different to the Red Hat Enterprise Linux structureand the reasoning for this is as follows:

Native Solaris packages require the absolute location

Solaris operating systems (and other non-Red Hat Enterprise Linux platforms) must ship andbuild all the dependent components such as openldap, openssl, db4 and cyrus-sasl toname a few.

2.8. Running on a Solaris Operating System Installation

Red Hat Enterprise Web Server consists of Apache Httpd and Apache Tomcat and the set ofcomponents needed to run them. These components can be run with the following users and groupswho are created after installation:

Running Tomcat version 5 or 6

In order to run Tomcat on the Solaris operating system, some service configuration files will needmanual editing.

Editing the Tomcat service entails uncommenting and setting the JAVA_HOME variable to the desiredJDK in the configuration file. The configuration file can be found at:

For Tomcat 5:

For Tomcat 6:

To run Tomcat 5 or 6, the following command must be run as root:

For Tomcat 5:

For Tomcat 6:

/opt/redhat/ews/etc/sysconfig/tomcat5

/opt/redhat/ews/etc/sysconfig/tomcat6

sbin/tomcat5 start

2. INSTALLATION NOTES

17

By running one of the above commands, the configuration file is read and the user and group arechanged to that of the tomcat user account before the catalina.sh script is executed.

The catalina.sh script file can be found within:

For Tomcat 5:

For Tomcat 6:

To stop Tomcat, one of the following commands can be executed:

For Tomcat 5:

For Tomcat 6:

By default, tomcat-native is automatically added to the LD_LIBRARY_PATH and -Djava.library.path during Tomcat startup. The catalina.sh script detects the running JVMversion and adds the /opt/redhat/ews/lib path (/opt/redhat/ews/lib64 for 64 bit JVM) to thelibrary path.

To run Tomcat as a service, use the provided scripts within the /opt/redhat/ews/etc/init.ddirectory. The following commands can be used to copy the necessary scripts:

For Tomcat 5:

For Tomcat 6:

For information on how to choose the init level numbers, consult your Solaris operating systemdocumentation. The preferred method of service management is through the Solaris Service Management Facility. In order to read more about this facility, consult the smf(5) manual.

Running the HTTP Server

Apache httpd configuration files are located inside the /opt/redhat/ews/etc/httpd directory. Bydefault all supported modules are loaded and enabled, so it is advised that you edit the httpd.conf fileand disable the modules you don't need.

Starting the HTTP server is performed using the provided apachectl script located inside the

sbin/tomcat6 start

/opt/redhat/ews/share/tomcat5/bin

/opt/redhat/ews/share/tomcat6/bin

sbin/tomcat5 stop

sbin/tomcat6 stop

cp /opt/redhat/ews/etc/init.d/tomcat6 /etc/rc3.d/S70tomcat5cp /opt/redhat/ews/etc/init.d/tomcat6 /etc/rcS.d/K20tomcat5

cp /opt/redhat/ews/etc/init.d/tomcat6 /etc/rc3.d/S70tomcat6cp /opt/redhat/ews/etc/init.d/tomcat6 /etc/rcS.d/K20tomcat6

Release Notes 1.0.1

18

/opt/redhat/ews/sbin directory. The apachectl script uses the configuration script, where youcan edit and select various startup parameters, including the running of mpm. The file used is /opt/redhat/ews/etc/sysconfig/httpd

To start the HTTP Server, use the following command:

To stop the HTTP Server, use the following command:

If you want your server to continue running automatically after a system reboot, a call to the apachectlscript should be added to your system startup files.

NOTE

For complete documentation on how to start and stop the HTTP Server, refer to the files, docs/httpd/invoking.html and docs/httpd/stopping.html respectively.

Running the mod_jk

Running mod_jk on the Solaris operating system is the same as running the package on Red HatEnterprise Linux installed via zip. For detailed instructions see Running the mod_jk

2.9. Uninstalling the package in the Solaris operating sytem

Uninstalling the Enterprise Web Server in the Solaris operating system is achieved by first executing:

Following this, the run-time files have to be manually removed. The directories requiring manual removalare:

/opt/redhat/ews

/var/run/tomcat5

/var/run/tomcat6

/var/cache/tomcat5

/var/cache/tomcat6

/var/log/httpd

/var/cache/mod_ssl

/var/cache/mod_proxy

2.10. Source Files

SRPMs

sbin/apachectl start

sbin/apachectl stop

pkgrm RHATews

2. INSTALLATION NOTES

19

ftp://ftp.redhat.com/pub/redhat/jbeap/ews/1.0.1/en/source

Source ZIP

ftp://ftp.redhat.com/pub/redhat/jbews/1.0.1/en/source/jboss-ews-src-1.0.1.zip

2.11. Excluded, Removed and Deprecated Items

This section outlines the items which are excluded from this release, deprecated or removed. In order tomaintain a high level of backwards compatibility and customer service, an item will usually be deprecatedbefore it is removed from a release.

NOTE

The difference between an excluded item and a removed item is that an excluded item isone that is commonly apart of a component of the JBoss Enterprise Web Server but hasnever featured within a JBoss Enterprise Web Framework release. However, a removeditem is one that has previously been in a release of the JBoss Enterprise Web Server andis no longer included.

2.11.1. Excluded Items

The following items have been excluded from this release of the JBoss Enterprise Web Server:

Tomcat Clustering has been excluded from the Apache Tomcat 6 component.Specifically the catalina-tribes.jar file has been removed. This has occurred to eliminateany possibility of session replication and because Red Hat does not believe this feature issuitable for medium or large scale production deployments.

2.11.2. Deprecated Items

The following items have been deprecated for this release of the JBoss Enterprise Web Server:

The Tomcat Clustering feature of Apache Tomcat 5 is marked as deprecated for thisrelease. Specifically the catalina-cluster.jar file has been deprecated.

2.11.3. Removed Items

None.

2.12. Product Support and License Website Links

Product Page

http://www.jboss.com/products/platforms/webserver/

Support Processes

http://www.redhat.com/support/process/

Production Support Scope of Coverage

http://www.redhat.com/support/policy/soc/production

Production Support Service Level Agreement

Release Notes 1.0.1

20

http://www.redhat.com/support/policy/sla/production/

Developer Support Scope of Coverage

http://www.redhat.com/support/policy/soc/developer/

Developer Support Service Level Agreement

http://www.redhat.com/support/policy/sla/developer/

Product Update and Support Policy by Product

http://www.redhat.com/security/updates/jboss_notes/

JBoss End User License Agreement

http://www.redhat.com/licenses/jboss_eula.html

2.13. Issues fixed in this release

The following sections detail the issues fixed in this release of JBoss Enterprise Web Server. Updates forsome of these issues have been made available previously via Red Hat Network, and are listedalongside the appropriate Red Hat Security Advisory identifier.

2.13.1. Fixed Security Issues

CVE-2010-2086

JBoss Enterprise Web Server 1.0.0 ships with Apache MyFaces 1.1.0. Apache MyFaces 1.1.0 doesnot support encrypted view state. When the application's view state is not encrypted, it is possible foran attacker to supply a new or modified view object as part of a request. This allows remote attackersto conduct cross-site scripting (XSS) attacks or execute arbitrary Expression Language (EL)statements via vectors that involve modifying the serialized view object.

This issue is resolved in JBoss Enterprise Web Server 1.0.1 because it does not include ApacheMyFaces.

CVE-2009-3555

A flaw was found in the way the TLS/SSL (Transport Layer Security/Secure Sockets Layer) protocolshandle session renegotiation on Red Hat Enterprise Linux 4 and 5. A man-in-the-middle attackercould use this flaw to prefix arbitrary plain text to a client's session (for example, an HTTPSconnection to a website). This could force the server to process an attacker's request as ifauthenticated using the victim's credentials.

Refer to the following Knowledgebase article for more information about how this issue affects JBossEnterprise Web Server: http://kbase.redhat.com/faq/docs/DOC-20491

CVE-2009-3095

A flaw was found in the Apache mod_proxy_ftp module on Red Hat Enterprise Linux 4 and 5 suchthat, in a reverse proxy configuration, a remote attacker could bypass intended access restrictions bycreating a HTTP Authorization header and send arbitrary commands to the FTP server. (RHSA-2010:0011)

CVE-2009-3094

A NULL pointer dereference flaw was found in the Apache mod_proxy_ftp module on Red HatEnterprise Linux 4 and 5. A malicious FTP server to which requests were proxied could use this flawto crash an httpd child process through a malformed reply to the EPSV or PASV commands, resulting

2. INSTALLATION NOTES

21

in a limited denial of service. (RHSA-2010:0011)

CVE-2009-2902

A directory traversal flaw was found in the Tomcat deployment process. WAR file names were notbeing sanitized during Tomcat deployment in Red Hat Enterprise Linux 4 and 5. This could allowattackers to create a specially-crafted WAR file that could delete files in the Tomcat host's workdirectory. (RHSA-2010:0119)

CVE-2009-2699

A flaw was found in the way errors were handled in the Event Port back end in the Apache PortableRuntime (APR) library, used by the Apache HTTP Server. If an error was incorrectly handled whileprocessing HTTP requests, httpd could hang. Note: This flaw only affected users running JBossEnterprise Web Server on the Solaris operating system.

CVE-2009-2693

A directory traversal flaw was found in the Tomcat deployment process. An attacker could create aspecially-crafted WAR file which, once deployed by an unsuspecting local user, would lead toattacker-controlled content being deployed outside the web root, into directories accessible to theTomcat process. (RHSA-2010:0119)

CVE-2009-2412

Multiple integer overflow flaws that led to heap-based buffer overflows were found in the way theApache Portable Runtime (APR) included in httpd22 manages memory pool and relocatable memoryallocations on Red Hat Enterprise Linux 4. An attacker could use these flaws to issue a specially-crafted request for memory allocation, which would lead to a denial of service (application crash) or,potentially, execute arbitrary code with the privileges of an application using the APR libraries.(RHSA-2009:1462)

CVE-2009-1955

A denial of service flaw was found in the Apache HTTP Server apr-util Extensible Markup Language(XML) parser for Red Hat Enterprise Linux 4. A remote attacker could create a specially-crafted XMLdocument that would cause excessive memory consumption when processed by the XML decodingengine. (RHSA-2009:1160)

CVE-2009-1891

A denial of service flaw was found in the Apache HTTP Server mod_deflate module for Red HatEnterprise Linux 4 and 5. This module continued to compress large files until compression wascomplete, even if the network connection that requested the content was closed before compressioncompleted. This caused mod_deflate to consume large amounts of CPU if mod_deflate was enabledfor a large file. (RHSA-2009:1155, RHSA-2009:1160)

CVE-2009-1890

A denial of service flaw was found in the Apache HTTP Server mod_proxy module when it was usedas a reverse proxy on Red Hat Enterprise Linux 4 and 5. A remote attacker could use this flaw toforce a proxy process to consume large amounts of CPU time. (RHSA-2009:1155, RHSA-2009:1160)

CVE-2009-1195

In Apache HTTP Server on Red Hat Enterprise Linux 4 and 5, in configurations using the AllowOverride directive with certain Options= arguments, local users were not restricted fromexecuting commands from a Server-Side-Include script as intended. (RHSA-2009:1155, RHSA-2009:1160)

Release Notes 1.0.1

22

CVE-2009-0783

In Tomcat 5 and 6 on Red Hat Enterprise Linux 4 and 5, web applications containing their own XMLparsers could replace the XML parser that Tomcat uses to parse configuration files. A malicious webapplication running on a Tomcat instance could read or, potentially, modify the configuration andXML-based data of other web applications deployed on the same Tomcat instance. (RHSA-2009:1506, RHSA-2009:1454)

CVE-2009-0580

In Tomcat 5 and 6 on Red Hat Enterprise Linux 4 and 5, the error checking methods of certainauthentication classes did not have sufficient error checking, allowing remote attackers toennumerate (via brute force methods) usernames registered with applications running on Tomcatwhen FORM-based authentication was used. (RHSA-2009:1506, RHSA-2009:1454)

CVE-2009-0033

A flaw was found in the way that the Tomcat 5 and 6 AJP (Apache JServ Protocol) connectorprocessed AJP connections on Red Hat Enterprise Linux 4 and 5. An attacker could use this flaw tosend specially-crafted requests that would cause a temporary denial of service. (RHSA-2009:1506,RHSA-2009:1454)

CVE-2009-0023

A heap-based underwrite flaw was discovered in the way Apache HTTP Server's apr-util librarycreated compiled forms of particular search patterns on Red Hat Enterprise Linux 4. An attacker couldformulate a specially-crafted search keyword that would overwrite arbitrary heap memory locatonswhen processed by the pattern preparation engine. (RHSA-2009:1160)

CVE-2008-5515

In Tomcat 5 and 6 on Red Hat Enterprise Linux 4 and 5, request dispatchers did not properlynormalize user requests that had trailing query strings, which allowed remote attackers to sendspecially-crafted requests that would cause an information leak. (RHSA-2009:1506, RHSA-2009:1454)

CVE-2007-5333

Tomcat 5 did not properly handle a certain character sequence in cookie values on Red HatEnterprise Linux 4 and 5. A remote attacker could use this flaw to obtain sensitive information, suchas session IDs, and use this information for session hijacking attacks. (RHSA-2009:1454)

NOTE

Version 0 cookies that contain values that must be quoted to be valid are automaticallychanged to version 1 cookies. To reactivate the previous, but insecure, behavior, addthe following entry to /etc/tomcat5/catalina.properties

CVE-2009-1191

An information disclosure flaw was found in Apache HTTP Server's mod_proxy_ajp module. Incertain situations, if a user sent a specially-crafted HTTP request, the httpd server could return aresponse intended for another user. (RHSA-2009:1058)

org.apache.tomcat.util.http.ServerCookie.VERSION_SWITCH=false

2. INSTALLATION NOTES

23

2.13.2. General Fixed Issues

JBPAPP-3272

Installing the tomcat5-admin-webapps package resulted in missing dependencies. This made itimpossible to access the Tomcat Administration section from http://localhost:8080/. The missingdependency, jakarta-commons-chain, has been added.

JBPAPP-3255

The zip distribution of Enterprise Web Server 1.0 did not contain the administration web application,and directed users to download and install tomcat5-admin-webapps separately. The package isnow included in the zip distribution.

JBPAPP-2850

Apache HTTP Server Control Interface (apachectl) required several modifications to work withEnterprise Web Server. The httpd/.postinstall script has been updated to make thesemodifications automatically.

JBPAPP-2122

The apachectl binary available from the Customer Service Portal for Red Hat Enterprise Linux 4 andRed Hat Enterprise Linux 5 i386 was zero length. The fix for this caused problems with the RPMdistribution. This has been corrected.

JBPAPP-1838

When Enterprise Web Server was installed by zip, the httpd/.postinstall script did not modifythe conf/httpd.conf file to point to the correct ServerRoot directory.

JBPAPP-1837

Following RPM installation on Red Hat Enterprise Linux 4, the /var/log/httpd22 directory was notautomatically created, which forced the httpd startup script to fail. The directory is now created onstartup.

JBPAPP-1809

Some Tomcat users would receive a warning that there were no write permissions on the directory.This problem can no longer be reproduced.

JBPAPP-1788

Tomcat 6 on the Solaris operating system stopped at the command /ews/etc/init.d/tomcat6 stop, and though the server terminated successfully, the output displayed command usage errorsbecause the CATALINA_PID variable was not defined in Tomcat 6. CATALINA_PID is now definedand the command usage errors no longer occur.

JBPAPP-1783

Two Tomcat Native libraries, libapr and libaprutil have been included in Enterprise WebServer to prevent problems when running Enterprise Web Server on Red Hat Enterprise Linux 5.

2.13.3. Known Issues with this release

Following is a list of known issues at the time of release.

Release Notes 1.0.1

24

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 6is 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

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

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 SecurityManager, Tomcat 6 does not start.

JBPAPP-3755

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

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 undeployapplications from your server.

JBPAPP-3735

The Apache HTTP Server module mod_ssl provides an interface to the OpenSSL library, whichprovides Strong Encryption using the Transport Layer Security/Secure Sockets Layer securityprotocols. 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 packagesfrom the Red Hat Enterprise Linux 5 base channel instead of the JBoss Enterprise Web Serverchannel. The installation instructions have been modified to include a work-around for this issue.

JBPAPP-3685

2. INSTALLATION NOTES

25

Attempting to edit server configuration details with the Tomcat 5 administration application results insome configuration information being lost from the configuration file (server.xml). At present we donot 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 JBossEnterprise 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 tobe fixed for JBoss Enterprise Web Server 1.0.2.

JBPAPP-3644

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

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 asexpected, but the newly created host is not persistently added to the Tomcat configuration. Only thelocalhost is listed after server restart. This is a problem upstream and is expected to be fixed forJBoss 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 aproblem 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 resultin a HTTP 404 Error. To work around this issue, add the following section to the WEB-INF/web.xmldescriptor, immediately after the servlet-mapping section:

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 becausethe AJP Connector continues to wait for a client connection during shutdown. This is a problemupstream and is expected to be fixed for JBoss Enterprise Web Server 1.0.2.

catalina.sh start -secure

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

Release Notes 1.0.1

26

JBPAPP-2852

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

JBPAPP-2655

jaxp_parser_impl.jar and xml-commons-apis.jar are not included in Tomcat 6. This cancause 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 JAXPimplementation (JAXP 1.3) is built into JDK5. If users require encoding that is not supported by JAXP1.3, the user must provide an external implementation of that encoding. The workaround for themissing 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 channelmeans that the httpd-devel may not be properly installed to the Red Hat Enterprise Linux x86_64from the JBoss Enterprise Web Server channel. The correct way to install this package is to run thefollowing command:

JBPAPP-1966

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

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

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

yum install httpd-devel.x86_64

2. INSTALLATION NOTES

27

A. REVISION HISTORY

Revision 2.3.0-0.1 Wed Feb 11 2015 Lucas CostiUpdated the Product Name to reflect the new name grouping for the product. No update was made to details in the guide.

Revision 1.0.1-13 Tue Jun 21 2011 Rebecca NewtonUpdating for security fixes.

Revision 2.3.0-0 Mon Dec 20 2010 Rebecca NewtonUpdating CVE descriptions.

Revision 2.2.0-0 Thu Oct 07 2010 Rebecca NewtonRetagging for Publican update.

Revision 2.1.0-0 Mon Feb 22 2010 Laura BaileyCorrected CVE descriptions.

Release Notes 1.0.1

28