Deregistering A Broker From A GlassFish Message Queue Cluster Removes All Destinations
(Doc ID 1466566.1)
Last updated on JULY 06, 2020
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.
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:
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