JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle GlassFish Server 3.1-3.1.1 High Availability Administration Guide
search filter icon
search icon

Document Information


1.  High Availability in GlassFish Server

2.  Setting Up SSH for Centralized Administration

3.  Administering GlassFish Server Nodes

4.  Administering GlassFish Server Clusters

5.  Administering GlassFish Server Instances

6.  Administering Named Configurations

7.  Configuring Web Servers for HTTP Load Balancing

8.  Configuring HTTP Load Balancing

9.  Upgrading Applications Without Loss of Availability

10.  Configuring High Availability Session Persistence and Failover

11.  Configuring Java Message Service High Availability

12.  RMI-IIOP Load Balancing and Failover


General Requirements for Configuring Load Balancing

Load Balancing Models

InitialContext Load Balancing

InitialContext Summary

InitialContext Algorithm

Enabling RMI-IIOP Hardware Load Balancing and Failover

To Enable RMI-IIOP Hardware Load Balancing for the Application Client Container

Per-Request Load Balancing (PRLB)

PRLB Summary

Enabling Per-Request Load Balancing

To Enable RMI-IIOP Per-Request Load Balancing for a Stateless EJB



With RMI-IIOP load balancing, IIOP client requests are distributed to different server instances or name servers. The goal is to spread the load evenly across the cluster, thus providing scalability. IIOP load balancing combined with EJB clustering and availability also provides EJB failover.

The following topics are addressed here:

General Requirements for Configuring Load Balancing

Oracle GlassFish Server provides high availability of remote EJB references and NameService objects over RMI-IIOP, provided all the following apply:

GlassFish Server supports load balancing for Java applications executing in the Application Client Container (ACC). See Enabling RMI-IIOP Hardware Load Balancing and Failover.

Note - GlassFish Server does not support RMI-IIOP load balancing and failover over secure sockets layer (SSL).

Load Balancing Models

GlassFish Server supports two general models for load balancing:

InitialContext Load Balancing

When a client performs a JNDI lookup for an object, the Naming Service creates a InitialContext (IC) object associated with a particular server instance. From then on, all lookup requests made using that IC object are sent to the same server instance. InitialContext load balancing can be configured automatically across an entire cluster.

Per-Request Load Balancing (PRLB)

Per Request Load Balancing (PRLB) is a method for load balancing stateless EJBs that enables load-balancing for each request to an EJB instance. PRLB chooses the first node in a cluster to use on each request. PRLB is configured on a per-EJB basis.