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

About GlassFish Server Clusters

Group Management Service

GMS Configuration Settings

Dotted Names for GMS Settings

To Preconfigure Nondefault GMS Configuration Settings

To Change GMS Settings After Cluster Creation

To Check the Health of Instances in a Cluster

To Validate That Multicast Transport Is Available for a Cluster

Using the Multi-Homing Feature With GMS

Traffic Separation Using Multi-Homing

Creating, Listing, and Deleting Clusters

To Create a Cluster

To List All Clusters in a Domain

To Delete a Cluster

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


Chapter 4

Administering GlassFish Server Clusters

A cluster is a collection of GlassFish Server instances that work together as one logical entity. A cluster provides a runtime environment for one or more Java Platform, Enterprise Edition (Java EE) applications. A cluster provides high availability through failure protection, scalability, and load balancing.

The Group Management Service (GMS) enables instances to participate in a cluster by detecting changes in cluster membership and notifying instances of the changes. To ensure that GMS can detect changes in cluster membership, a cluster's GMS settings must be configured correctly.

The following topics are addressed here: