Skip Navigation Links | |
Exit Print View | |
Oracle GlassFish Server 3.1-3.1.1 High Availability Administration Guide |
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
Using Message Queue Broker Clusters With GlassFish Server
About Message Queue Broker Clusters
Configuring GlassFish Clusters to Use Message Queue Broker Clusters
To Change the Master Broker in an Embedded or Local Broker Cluster
To Migrate Between Types of Embedded or Local Conventional Broker Clusters
To Configure a GlassFish Cluster to Use a Local Enhanced Broker Cluster
To Configure a GlassFish Cluster to Use a Remote Broker Cluster
When a message-driven bean (MDB) application is deployed to a GlassFish cluster, incoming messages are delivered randomly to MDBs without regard to the cluster instances in which they are running.
If the MDB is configured to receive messages from a durable or non-durable subscription on a topic, then only one MDB instance across the whole GlassFish cluster will receive each message.
For more information about these features, see About Shared Topic Subscriptions for Clustered Containers in Oracle GlassFish Server Message Queue 4.5 Administration Guide.