The broker configuration MBean has the following object name:

com.sun.messaging.jms.server:type=Broker,subtype=Config

A string representing this object name is defined as a static constant BROKER_CONFIG_MBEAN_NAME in the utility class MQObjectName.

The broker configuration MBean has the attributes shown in Table 3-1. The names of these attributes are defined as static constants in the utility class BrokerAttributes.

Table 3-1 Broker Configuration Attributes

The broker configuration MBean supports the operations shown in Table 3-2. The names of these operations are defined as static constants in the utility class BrokerOperations.

Table 3-2 Broker Configuration Operations

^Footnote 1 HA clusters only

The broker configuration MBean supports the notification shown in Table 3-3.

Table 3-3 Broker Configuration Notification

The broker monitor MBean has the following object name:

com.sun.messaging.jms.server:type=Broker,subtype=Monitor

A string representing this object name is defined as a static constant BROKER_MONITOR_MBEAN_NAME in the utility class MQObjectName.

The broker monitor MBean has the attributes shown in Table 3-4. The names of these attributes are defined as static constants in the utility class BrokerAttributes.

Table 3-4 Broker Monitor Attributes

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

^Footnote 1 HA clusters only

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

Table 3-6 Data Retrieval Methods for Broker Monitor Notifications

^Footnote 1 HA clusters only

The service configuration MBean has an object name of the following form:

`com.sun.messaging.jms.server:type=Service,subtype=Config,name=`serviceName

where serviceName is the name of the connection service (see Table 3-7). The utility class MQObjectName provides a static method, createServiceConfig, for constructing object names of this form.

Table 3-7 Connection Service Names for Service Configuration MBeans

The service configuration MBean has the attributes shown in Table 3-8. The names of these attributes are defined as static constants in the utility class ServiceAttributes.

Table 3-8 Service Configuration Attributes

The service configuration MBean supports the operations shown in Table 3-9. The names of these operations are defined as static constants in the utility class ServiceOperations.

Table 3-9 Service Configuration Operations

The service configuration MBean supports the notification shown in Table 3-10.

Table 3-10 Service Configuration Notification

The service monitor MBean has an object name of the following form:

`com.sun.messaging.jms.server:type=Service,subtype=Monitor,name=`serviceName

where serviceName is the name of the connection service (see Table 3-11). The utility class MQObjectName provides a static method, createServiceMonitor, for constructing object names of this form.

Table 3-11 Connection Service Names for Service Monitor MBeans

The service monitor MBean has the attributes shown in Table 3-12. The names of these attributes are defined as static constants in the utility class ServiceAttributes.

Table 3-12 Service Monitor Attributes

Table 3-13 shows the possible values for the State and StateLabel attributes. These values are defined as static constants in the utility class ServiceState.

Table 3-13 Connection Service State Values

The service monitor MBean supports the operations shown in Table 3-14. The names of these operations are defined as static constants in the utility class ServiceOperations.

Table 3-14 Service Monitor Operations

The service monitor MBean supports the notifications shown in Table 3-15. These notifications are instances of the Message Queue JMX classes ServiceNotification and ConnectionNotification, and their names are defined as static constants in those classes.

Table 3-15 Service Monitor Notifications

Table 3-16 shows the method defined in class ServiceNotification for obtaining details about a service monitor notification. See Table 3-31 for the corresponding methods of class ConnectionNotification.

Table 3-16 Data Retrieval Method for Service Monitor Notifications

The service manager configuration MBean has the following object name:

com.sun.messaging.jms.server:type=ServiceManager,subtype=Config

A string representing this object name is defined as a static constant SERVICE_MANAGER_CONFIG_MBEAN_NAME in the utility class MQObjectName.

The service manager configuration MBean has the attributes shown in Table 3-17. The names of these attributes are defined as static constants in the utility class ServiceAttributes.

Table 3-17 Service Manager Configuration Attributes

The service manager configuration MBean supports the operations shown in Table 3-18. The names of these operations are defined as static constants in the utility class ServiceOperations.

Table 3-18 Service Manager Configuration Operations

The service manager monitor MBean has the following object name:

com.sun.messaging.jms.server:type=ServiceManager,subtype=Monitor

A string representing this object name is defined as a static constant SERVICE_MANAGER_MONITOR_MBEAN_NAME in the utility class MQObjectName.

The service manager monitor MBean has the attributes shown in Table 3-19. The names of these attributes are defined as static constants in the utility class ServiceAttributes.

Table 3-19 Service Manager Monitor Attributes

The service manager monitor MBean supports the operation shown in Table 3-20. The name of this operation is defined as a static constant in the utility class ServiceOperations.

Table 3-20 Service Manager Monitor Operation

The service manager monitor MBean supports the notifications shown in Table 3-21. These notifications are instances of the Message Queue JMX class ServiceNotification, and their names are defined as static constants in that class.

Table 3-21 Service Manager Monitor Notifications

Table 3-22 shows the method defined in class ServiceNotification for obtaining details about a service manager monitor notification.

Table 3-22 Data Retrieval Method for Service Manager Monitor Notifications

The connection configuration MBean has an object name of the following form:

`com.sun.messaging.jms.server:type=Connection,subtype=Config,id=`connectionID

where connectionID is the connection identifier. For example:

The utility class MQObjectName provides a static method, createConnectionConfig, for constructing object names of this form.

The connection configuration MBean has the attribute shown in Table 3-23. The name of this attribute is defined as a static constant in the utility class ConnectionAttributes.

Table 3-23 Connection Configuration Attribute

The connection monitor MBean has an object name of the following form:

`com.sun.messaging.jms.server:type=Connection,subtype=Monitor,id=`connectionID

where connectionID is the connection identifier. For example:

The utility class MQObjectName provides a static method, createConnectionMonitor, for constructing object names of this form.

The connection monitor MBean has the attributes shown in Table 3-24. The names of these attributes are defined as static constants in the utility class ConnectionAttributes.

Table 3-24 Connection Monitor Attributes

The connection monitor MBean supports the operations shown in Table 3-25. The names of these operations are defined as static constants in the utility class ConnectionOperations.

Table 3-25 Connection Monitor Operations

The connection manager configuration MBean has the following object name:

com.sun.messaging.jms.server:type=ConnectionManager,subtype=Config

A string representing this object name is defined as a static constant CONNECTION_MANAGER_CONFIG_MBEAN_NAME in the utility class MQObjectName.

The connection manager configuration MBean has the attribute shown in Table 3-26. The name of this attribute is defined as a static constant in the utility class ConnectionAttributes.

Table 3-26 Connection Manager Configuration Attribute

The connection manager configuration MBean supports the operations shown in Table 3-27. The names of these operations are defined as static constants in the utility class ConnectionOperations.

Table 3-27 Connection Manager Configuration Operations

The connection manager monitor MBean has the following object name:

com.sun.messaging.jms.server:type=ConnectionManager,subtype=Monitor

A string representing this object name is defined as a static constant CONNECTION_MANAGER_MONITOR_MBEAN_NAME in the utility class MQObjectName.

The connection manager monitor MBean has the attributes shown in Table 3-28. The names of these attributes are defined as static constants in the utility class ConnectionAttributes.

Table 3-28 Connection Manager Monitor Attributes

The connection manager monitor MBean supports the operation shown in Table 3-29. The name of this operation is defined as a static constant in the utility class ConnectionOperations.

Table 3-29 Connection Manager Monitor Operation

The connection manager monitor MBean supports the notifications shown in Table 3-30. These notifications are instances of the Message Queue JMX class ConnectionNotification, and their names are defined as static constants in that class.

Table 3-30 Connection Manager Monitor Notifications

Table 3-31 shows the methods defined in class ConnectionNotification for obtaining details about a connection manager monitor notification.

Table 3-31 Data Retrieval Methods for Connection Manager Monitor Notifications

The destination configuration MBean has an object name of the following form:

where destinationType is one of the destination types shown in Table 3-33 and destinationName is the name of the destination. For example:

The utility class MQObjectName provides a static method, createDestinationConfig, for constructing object names of this form.

The destination configuration MBean has the attributes shown in Table 3-32. The names of these attributes are defined as static constants in the utility class DestinationAttributes.

Table 3-32 Destination Configuration Attributes

^Footnote 1 Queue destinations only

Table 3-33 shows the possible values for the Type attribute. These values are defined as static constants in the utility class DestinationType.

Table 3-33 Destination Configuration Type Values

Table 3-34 shows the possible values for the LimitBehavior attribute. These values are defined as static constants in the utility class DestinationLimitBehavior.

Table 3-34 Destination Limit Behaviors

The destination configuration MBean supports the operations shown in Table 3-35. The names of these operations are defined as static constants in the utility class DestinationOperations.

Table 3-35 Destination Configuration Operations

^Footnote 1 File-based persistence only

Table 3-36 shows the possible values for the pause operation’s pauseType parameter. These values are defined as static constants in the utility class DestinationPauseType.

Table 3-36 Destination Pause Types

The destination configuration MBean supports the notification shown in Table 3-37.

Table 3-37 Destination Configuration Notification

The destination monitor MBean has an object name of the following form:

where destinationType is one of the destination types shown in Table 3-39 and destinationName is the name of the destination. For example:

The utility class MQObjectName provides a static method, createDestinationMonitor, for constructing object names of this form.

The destination monitor MBean has the attributes shown in Table 3-38. The names of these attributes are defined as static constants in the utility class DestinationAttributes.

Table 3-38 Destination Monitor Attributes

^Footnote 1 Temporary destinations only

^Footnote 2 Queue destinations only

^Footnote 3 File-based persistence only

Table 3-39 shows the possible values for the Type attribute. These values are defined as static constants in the utility class DestinationType.

Table 3-39 Destination Monitor Type Values

Table 3-40 shows the possible values for the State and StateLabel attributes. These values are defined as static constants in the utility class DestinationState.

Table 3-40 Destination State Values

The destination monitor MBean supports the operations shown in Table 3-41. The names of these operations are defined as static constants in the utility class DestinationOperations.

Table 3-41 Destination Monitor Operations

^Footnote 1 Temporary destinations only

^Footnote 2 Queue destinations only

The destination monitor MBean supports the notifications shown in Table 3-42. These notifications are instances of the Message Queue JMX class DestinationNotification, and their names are defined as static constants in that class.

Table 3-42 Destination Monitor Notifications

Table 3-43 shows the methods defined in class DestinationNotification for obtaining details about a destination monitor notification.

Table 3-43 Data Retrieval Methods for Destination Monitor Notifications

The destination manager configuration MBean has the following object name:

com.sun.messaging.jms.server:type=DestinationManager,subtype=Config

A string representing this object name is defined as a static constant DESTINATION_MANAGER_CONFIG_MBEAN_NAME in the utility class MQObjectName.

The destination manager configuration MBean has the attributes shown in Table 3-44. The names of these attributes are defined as static constants in the utility class DestinationAttributes.

Table 3-44 Destination Manager Configuration Attributes

^Footnote 1 Auto-created queue destinations only

The destination manager configuration MBean supports the operations shown in Table 3-45. The names of these operations are defined as static constants in the utility class DestinationOperations.

Table 3-45 Destination Manager Configuration Operations

^Footnote 1 File-based persistence only

Table 3-46 shows the possible values for the create and destroy operations' destinationType parameters. These values are defined as static constants in the utility class DestinationType.

Table 3-46 Destination Manager Configuration Type Values

Table 3-47 shows the possible values for the pause operation’s pauseType parameter. These values are defined as static constants in the utility class DestinationPauseType.

Table 3-47 Destination Manager Pause Types

The destination manager configuration MBean supports the notification shown in Table 3-48.

Table 3-48 Destination Manager Configuration Notification

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

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

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

The producer manager configuration MBean has the following object name:

com.sun.messaging.jms.server:type=ProducerManager,subtype=Config

A string representing this object name is defined as a static constant PRODUCER_MANAGER_CONFIG_MBEAN_NAME in the utility class MQObjectName.

The producer manager configuration MBean has the attribute shown in Table 3-53. The name of this attribute is defined as a static constant in the utility class ProducerAttributes.

Table 3-53 Producer Manager Configuration Attribute

The producer manager configuration MBean supports the operation shown in Table 3-54. The name of this operation is defined as a static constant in the utility class ProducerOperations.

Table 3-54 Producer Manager Configuration Operation

The producer manager monitor MBean has the following object name:

com.sun.messaging.jms.server:type=ProducerManager,subtype=Monitor

A string representing this object name is defined as a static constant PRODUCER_MANAGER_MONITOR_MBEAN_NAME in the utility class MQObjectName.

The producer manager monitor MBean has the attribute shown in Table 3-55. The name of this attribute is defined as a static constant in the utility class ProducerAttributes.

Table 3-55 Producer Manager Monitor Attribute

The producer manager monitor MBean supports the operations shown in Table 3-56. The names of these operations are defined as static constants in the utility class ProducerOperations.

Table 3-56 Producer Manager Monitor Operations

The getProducerInfoByID and getProducerInfo operations return objects implementing the JMX interface CompositeData, which maps lookup keys to associated data values. The keys shown in Table 3-57 are defined as static constants in the utility class ProducerInfo for use with these objects.

Table 3-57 Lookup Keys for Message Producer Information

Table 3-58 shows the possible values returned for the lookup key DestinationType. These values are defined as static constants in the utility class DestinationType.

Table 3-58 Message Producer Destination Types

The consumer manager configuration MBean has the following object name:

com.sun.messaging.jms.server:type=ConsumerManager,subtype=Config

A string representing this object name is defined as a static constant CONSUMER_MANAGER_CONFIG_MBEAN_NAME in the utility class MQObjectName.

The consumer manager configuration MBean has the attribute shown in Table 3-59. The name of this attribute is defined as a static constant in the utility class ConsumerAttributes.

Table 3-59 Consumer Manager Configuration Attribute

The consumer manager configuration MBean supports the operations shown in Table 3-60. The names of these operations are defined as static constants in the utility class ConsumerOperations.

Table 3-60 Consumer Manager Configuration Operations

^Footnote 1 Durable topic subscribers only

The consumer manager monitor MBean has the following object name:

com.sun.messaging.jms.server:type=ConsumerManager,subtype=Monitor

A string representing this object name is defined as a static constant CONSUMER_MANAGER_MONITOR_MBEAN_NAME in the utility class MQObjectName.

The consumer manager monitor MBean has the attribute shown in Table 3-61. The name of this attribute is defined as a static constant in the utility class ConsumerAttributes.

Table 3-61 Consumer Manager Monitor Attribute

The consumer manager monitor MBean supports the operations shown in Table 3-62. The names of these operations are defined as static constants in the utility class ConsumerOperations.

Table 3-62 Consumer Manager Monitor Operations

The getConsumerInfoByID and getConsumerInfo operations return objects implementing the JMX interface CompositeData, which maps lookup keys to associated data values. The keys shown in Table 3-63 are defined as static constants in the utility class ConsumerInfo for use with these objects.

Table 3-63 Lookup Keys for Message Consumer Information

^Footnote 1 Durable topic subscribers only

Table 3-64 shows the possible values returned for the lookup key DestinationType. These values are defined as static constants in the utility class DestinationType.

Table 3-64 Message Consumer Destination Types

Table 3-65 shows the possible values returned for the lookup keys AcknowledgeMode and AcknowledgeModeLabel. Four of these values are defined as static constants in the standard JMS interface jakarta.jms.Session; the fifth (NO_ACKNOWLEDGE) is defined in the extended Message Queue version of the interface, com.sun.messaging.jms.Session.

Table 3-65 Acknowledgment Modes

The transaction manager configuration MBean has the following object name:

com.sun.messaging.jms.server:type=TransactionManager,subtype=Config

A string representing this object name is defined as a static constant TRANSACTION_MANAGER_CONFIG_MBEAN_NAME in the utility class MQObjectName.

The transaction manager configuration MBean has the attribute shown in Table 3-66. The name of this attribute is defined as a static constant in the utility class TransactionAttributes.

Table 3-66 Transaction Manager Configuration Attribute

The transaction manager configuration MBean supports the operations shown in Table 3-67. The names of these operations are defined as static constants in the utility class TransactionOperations.

Table 3-67 Transaction Manager Configuration Operations

The transaction manager monitor MBean has the following object name:

com.sun.messaging.jms.server:type=TransactionManager,subtype=Monitor

A string representing this object name is defined as a static constant TRANSACTION_MANAGER_MONITOR_MBEAN_NAME in the utility class MQObjectName.

The transaction manager monitor MBean has the attributes shown in Table 3-68. The names of these attributes are defined as static constants in the utility class TransactionAttributes.

Table 3-68 Transaction Manager Monitor Attributes

The transaction manager monitor MBean supports the operations shown in Table 3-69. The names of these operations are defined as static constants in the utility class TransactionOperations.

Table 3-69 Transaction Manager Monitor Operations

The getTransactionInfoByID and getTransactionInfo operations return objects implementing the JMX interface CompositeData, which maps lookup keys to associated data values. The keys shown in Table 3-70 are defined as static constants in the utility class TransactionInfo for use with these objects.

Table 3-70 Lookup Keys for Transaction Information

^Footnote 1 Distributed transactions only

Table 3-71 shows the possible values returned for the lookup keys State and StateLabel. These values are defined as static constants in the utility class TransactionState.

Table 3-71 Transaction State Values

^Footnote 1 Distributed transactions only

The transaction manager monitor MBean supports the notifications shown in Table 3-72. These notifications are instances of the Message Queue JMX class TransactionNotification, and their names are defined as static constants in that class.

Table 3-72 Transaction Manager Monitor Notifications

^Footnote 1 Distributed transactions only

Table 3-73 shows the method defined in class TransactionNotification for obtaining details about a transaction manager monitor notification.

Table 3-73 Data Retrieval Method for Transaction Manager Monitor Notifications

The cluster configuration MBean has the following object name:

com.sun.messaging.jms.server:type=Cluster,subtype=Config

A string representing this object name is defined as a static constant CLUSTER_CONFIG_MBEAN_NAME in the utility class MQObjectName.

The cluster configuration MBean has the attributes shown in Table 3-74. The names of these attributes are defined as static constants in the utility class ClusterAttributes.

Table 3-74 Cluster Configuration Attributes

^Footnote 1 HA clusters only

^Footnote 2 Conventional clusters only

The cluster configuration MBean supports the operations shown in Table 3-75. The names of these operations are defined as static constants in the utility class ClusterOperations.

Table 3-75 Cluster Configuration Operations

^Footnote 1 HA clusters only

^Footnote 2 Conventional clusters only

The LocalBrokerInfo and MasterBrokerInfo attributes and the getBrokerInfoByAddress, getBrokerInfoByID, and getBrokerInfo operations return objects implementing the JMX interface CompositeData, which maps lookup keys to associated data values. The keys shown in Table 3-76 are defined as static constants in the utility class BrokerClusterInfo for use with these objects.

Table 3-76 Lookup Keys for Cluster Configuration Information

^Footnote 1 HA clusters only

The changeMasterBroker operation returns an object implementing the JMX interface CompositeData, which maps lookup keys to associated data values. The keys shown in Table 3-77 are defined as static constants in the utility class ChangeMasterBrokerResultInfo for use with this object.

Table 3-77 Lookup Keys for changeMasterBroker

The cluster configuration MBean supports the notification shown in Table 3-78.

Table 3-78 Cluster Configuration Notification

The cluster monitor MBean has the following object name:

com.sun.messaging.jms.server:type=Cluster,subtype=Monitor

A string representing this object name is defined as a static constant CLUSTER_MONITOR_MBEAN_NAME in the utility class MQObjectName.

The cluster monitor MBean has the attributes shown in Table 3-79. The names of these attributes are defined as static constants in the utility class ClusterAttributes.

Table 3-79 Cluster Monitor Attributes