test

Oracle GlassFish Message Queue 4.4.2 Developer's Guide for JMX Clients

Notifications

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

Table 3–5 Broker Monitor Notifications

Name 

Utility Constant 

Description 

mq.broker.shutdown.start

BrokerNotification.BROKER_SHUTDOWN_START

Broker has begun shutting down 

mq.broker.quiesce.start

BrokerNotification.BROKER_QUIESCE_START

Broker has begun quiescing 

mq.broker.quiesce.complete

BrokerNotification.BROKER_QUIESCE_COMPLETE

Broker has finished quiescing 

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

BrokerNotification.BROKER_TAKEOVER_START

Broker has begun taking over persistent data store from another broker 

mq.broker.takeover.complete

BrokerNotification.BROKER_TAKEOVER_COMPLETE

Broker has finished taking over persistent data store from another broker 

mq.broker.takeover.fail

BrokerNotification.BROKER_TAKEOVER_FAIL

Attempted takeover has failed 

mq.broker.resource.state.change

BrokerNotification.BROKER_RESOURCE_STATE_CHANGE

Broker’s resource state has changed 

mq.cluster.broker.join

ClusterNotification.CLUSTER_BROKER_JOIN

Broker has joined a cluster 

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

Table 3–6 Data Retrieval Methods for Broker Monitor Notifications

Method 

Result Type 

Description 

getBrokerID

String

Broker identifier

getBrokerAddress

String

Broker address, in the form hostName:portNumber

Example:

    host1:3000


getFailedBrokerID [HA clusters only]

String

Broker identifier of broker being taken over

getOldResourceState

String

Broker’s previous resource state:  

    green: < 80% memory utilization


    yellow: 80–90% memory utilization


    orange: 90–98% memory utilization


    red: > 98% memory utilization


Note –

The threshold values shown are the default thresholds for triggering the various states; these can be changed by setting the broker configuration properties

    imq.green.threshold


    imq.yellow.threshold


    imq.orange.threshold


    imq.red.threshold


getNewResourceState

String

Broker’s new resource state (see getOldResourceState, above, for possible values)

getHeapMemoryUsage

MemoryUsage

Broker’s current heap memory usage 

The value returned is an object of class MemoryUsage (defined in the package java.lang.management).