Sun GlassFish Enterprise Server 2.1 Release Notes

Apache and Load Balancer Plugin

This section describes known Apache Web server and load balancer plugin issues and associated solutions.

Deployment of Java EE application with EJB as a Web Service is not captured by load balancing plug-in (Issue 685)


When you deploy any WAR (or EAR) with a servlet-based web service, the HTTP Load Balancer is updated with information about the web service. When an EJB-based web service is deployed, the configuration of the HTTP Load Balancer is not updated to reflect the new object.


Add these context roots manually to the load balancer configuration file (loadbalancer.xml). However, dynamic reconfiguration of load balancer configuration (using the auto-apply feature) would result in older manual edits being lost.

Turn off the auto-apply feature from DAS and instead use the manual export feature to edit and apply the load balancer configuration onto the Web Server.

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

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.

Must start Apache Web Server as root (6308021)

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


Group nobody

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