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
Name |
Type |
Settable? |
Description |
Integer |
No |
Current number of open transactions |
|
Long |
No |
Cumulative number of transactions committed since broker started |
|
Long |
No |
Cumulative number of transactions rolled back since broker started |
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
Name |
Parameters |
Result Type |
Description |
---|---|---|---|
None |
String[] | ||
transactionID (String) |
CompositeData |
Descriptive information about transaction The desired transaction is designated by its transaction identifier (transactionID). The value returned is a JMX CompositeData object describing the transaction; see Table 3–70 for lookup keys used with this object. |
|
None |
CompositeData[] |
Descriptive information about all current open transactions The value returned is an array of JMX CompositeData objects describing the transactions; see Table 3–70 for lookup keys used with these objects. |
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
Name |
Value Type |
Description |
---|---|---|
String | ||
String | ||
String |
User name |
|
String |
Client identifier |
|
String |
Connection string |
|
Long |
Time created, in standard Java format (milliseconds since January 1, 1970, 00:00:00 UTC) |
|
Integer |
Current state See Table 3–71 for possible values. |
|
String |
String representation of current state Useful for displaying the state in human-readable form, such as in the Java Monitoring and Management Console (jconsole). See Table 3–71 for possible values. |
|
Long |
Number of messages |
|
Long |
Number of acknowledgments |
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
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
Name |
Utility Constant |
Description |
---|---|---|
Transaction has entered prepared state |
||
Transaction committed |
||
Transaction rolled back |
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
Method |
Result Type |
Description |
---|---|---|
String |