Each broker has a single destination manager monitor MBean, used for managing all of the broker's destination monitor MBeans.
The destination manager monitor MBean has the following object name:
com.sun.messaging.jms.server:type=DestinationManager,subtype=Monitor
A string representing this object name is defined as a static constant DESTINATION_MANAGER_MONITOR_MBEAN_NAME in the utility class MQObjectName.
The destination manager monitor MBean has the attributes shown in Table 3–49. The names of these attributes are defined as static constants in the utility class DestinationAttributes.
Table 3–49 Destination Manager Monitor Attributes
The destination manager monitor MBean supports the operation shown in Table 3–50. The name of this operation is defined as a static constant in the utility class DestinationOperations.
Table 3–50 Destination Manager Monitor Operation
Name |
Parameters |
Result Type |
Description |
---|---|---|---|
None |
ObjectName[] |
Object names of destination monitor MBeans for all current destinations |
The destination manager monitor MBean supports the notifications shown in Table 3–51. These notifications are instances of the Message Queue JMX class DestinationNotification, and their names are defined as static constants in that class.
Table 3–51 Destination Manager Monitor Notifications
Name |
Utility Constant |
Description |
---|---|---|
Destination created |
||
Destination destroyed |
||
Destination paused |
||
Destination resumed |
||
Destination compacted |
||
Destination purged |
Table 3–52 shows the methods defined in class DestinationNotification for obtaining details about a destination manager monitor notification.
Table 3–52 Data Retrieval Methods for Destination Manager Monitor Notifications
Method |
Result Type |
Description |
---|---|---|
String |
Destination name |
|
String |
Destination type See Table 3–46 for possible values. |
|
Boolean |
Administrator-created destination? |
|
String |
Pause type See Table 3–47 for possible values. |