test

Sun Java System Message Queue 4.3 Developer's Guide for JMX Clients

Notifications

The cluster monitor MBean supports the notifications shown in Table 3–82. These notifications are instances of the Message Queue JMX classes ClusterNotification and BrokerNotification, and their names are defined as static constants in those classes.

Table 3–82 Cluster Monitor Notifications

Name 

Utility Constant 

Description 

mq.cluster.broker.join

ClusterNotification.CLUSTER_BROKER_JOIN

A broker has joined the cluster 

mq.cluster.broker.down

ClusterNotification.CLUSTER_BROKER_DOWN

A broker in the cluster has shut down or crashed 

mq.broker.takeover.start [HA clusters only]

BrokerNotification.BROKER_TAKEOVER_START

A broker has begun taking over persistent data store from another broker

mq.broker.takeover.complete

BrokerNotification.BROKER_TAKEOVER_COMPLETE

A broker has finished taking over persistent data store from another broker

mq.broker.takeover.fail

BrokerNotification.BROKER_TAKEOVER_FAIL

An attempted takeover has failed

Table 3–83 shows the methods defined in class ClusterNotification for obtaining details about a cluster monitor notification. See Table 3–6 for the corresponding methods of class BrokerNotification.

Table 3–83 Data Retrieval Methods for Cluster Monitor Notifications

Method 

Result Type 

Description 

isHighlyAvailable

Boolean

High-availability (HA) cluster?

getClusterID

String

Cluster identifier

getBrokerID

String

Broker identifier of affected broker

getBrokerAddress

String

Address of affected broker, in the form hostName:portNumber

Example:

    host1:3000


isMasterBroker [Conventional clusters only]

Boolean

Master broker affected?