Apache and Load Balancer Plugin

6306784 

The High-Availability Administration Guide contains incorrect instructions for using openssl with Apache.

Solution

When compiling and building openssl, run the following commands:

cd openssl-0.9.7e

config

make

Also, for Apache 1.3, the directory name of the mod_ssl source will vary depending upon the release of Apache used. For example, for Apache 1.3.33, the name is mod_ssl-2.8.22-1.3.33.

6307976 

The High-Availability Administration Guide does not contain instructions for using a certificate for Apache 2.0. 

Solution

To run Apache security, you must use a certificate. For instructions on obtaining a certificate from a certificate authority, see the information on certificates in the modssl FAQ.

6308021 

Must start Apache Web Server as root. 

Solution

On Solaris, if your Application Server was installed under root, you must start the Apache Web Server as root. Java Enterprise System installations are installed as root. For Apache 2.0, after starting as root, Apache switches and runs as another user you designate. You designate that user in the /conf/httpd.conf file. To start as root, on many systems you must edit the httpd.conf file to designate the correct group. Replace the line:

Group #-1

with 

Group nobody

More information on user/group use is included in the httpd.conf file.

6308043 

Addition to instructions for using openssl with Apache Web Server 2.0 on Solaris.

After installing Apache 2.0 and the load balancer plug-in, edit ssl.conf and sll-std.conf as follows:

Replace the line: 

<VirtualHost _default_:9191>

with 

<VirtualHost machine_name:9191>

Where machine_name is the name of your machine and 9191 is a security port number.

6338687 

Load Balancer Plugin URL/URI limit = 8K. 

There is a hard-coded limit of 8K for the length of URLs/URIs that can be parsed by the load balancer plugin in Application Server 8.1 Update 2. 

Solution

Do not create URLs or URIs greater than 8K in length and then send them to the Application Server by means of the load balancer plugin. 

6406884 

Problems using IIS6 and load balancer plugin with Application Server 8.1UR2. 

Solution

To use IIS6 and the load balancer plugin with Application Server 8.1UR2, you need to perform the following addition configuration steps: 

1. Add appserver-install-location/lib to the system path variable and then restart the machine.

2. Enable unknown Web service extensions, as described in the Microsoft Technet article Requests for dynamic content return 404 error (IIS 6.0).

3. Give NTFS write and modify permissions to the group IIS_WPG on the file inetput/wwwroot/sun-passthrough/lb.log. This is necessary because IIS 6.0 runs in Worker Process Isolation Mode, and it runs the IIS server with the security privileges of the group IIS_WPG. You will need to create this file and then right click on it to set security permissions.

If you do not see the status of the ISAPI filter going green, try sending any http request (do not worry if it fails here) to the IIS-http-port and then right-click on Web site and select properties and check the ISAPI filter.