My Oracle Support Banner

Deregistering A Broker From A GlassFish Message Queue Cluster Removes All Destinations (Doc ID 1466566.1)

Last updated on AUGUST 10, 2023

Applies to:

Sun Java System Message Queue - Version 4.4 and later
Oracle GlassFish Server - Version 3.1.1 and later
Information in this document applies to any platform.

Symptoms

A GlassFish Message Queue cluster running in a highly available (HA) configuration with Oracle JDBC as the persistence store with 2 broker nodes set up. The following command was executed to remove a broker "brokerToRemove" from the enhanced HA broker cluster because of the requirement to remove the node:

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.