| Skip Navigation Links | |
| Exit Print View | |
|
Oracle GlassFish Server Message Queue 4.5 Developer's Guide for JMX Clients |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Oracle GlassFish Server Message Queue 4.5 Developer's Guide for JMX Clients |
1. Introduction to JMX Programming for Message Queue Clients
3. Message Queue MBean Reference
Connection Manager Configuration
Destination Manager Configuration
Producer Manager Configuration
This section describes the MBeans used for managing transactions:
The transaction manager configuration MBean configures transactions.
The transaction manager monitor MBean monitors transactions.
The following subsections describe each of these MBeans in detail.
Note - Notice that there are no resource MBeans associated with individual transactions; rather, all transactions are managed through the broker's global transaction manager configuration and transaction manager monitor MBeans.
Each broker has a single transaction manager configuration MBean, used for configuring all of the broker's transactions.
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
|
Each broker has a single transaction manager monitor MBean, used for monitoring all of the broker's transactions.
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
|
1Distributed 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
|
1Distributed 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
|
1Distributed 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
|
|