| Oracle GlassFish Server Message Queue Developer's Guide for JMX Clients Release 4.5.2 Part Number E24946-01 |
|
|
View PDF |
| Oracle GlassFish Server Message Queue Developer's Guide for JMX Clients Release 4.5.2 Part Number E24946-01 |
|
|
View PDF |
This chapter describes the JMX MBeans that allow you to configure and monitor a Message Queue broker. It consists of the following sections:
This section describes the MBeans used for managing brokers:
The broker configuration MBean configures a broker.
The broker monitor MBean monitors a broker.
The following subsections describe each of these MBeans in detail.
The broker configuration MBean is used for configuring a broker. There is one such MBean for each broker.
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
| Name | Type | Settable? | Description |
|---|---|---|---|
|
|
|
No |
Broker identifier Must be a unique alphanumeric string of no more than n - 13 characters, where n is the maximum table name length allowed by the database. No two running brokers may have the same broker identifier. For brokers using a JDBC-based persistent data store, this string is appended to the names of all database tables to make them unique in the case where more than one broker instance is using the same database. If a database is not used as the persistent data store, the value of this attribute is Note: For high-availability brokers, database table names use the |
|
|
|
No |
Broker version |
|
|
|
No |
Broker instance name Example:
|
|
|
|
Yes |
Port number of Port Mapper |
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
| Name | Parameters | Result Type | Description |
|---|---|---|---|
|
|
nofailover ( time ( |
None |
Shut down broker If nofailover is The time parameter specifies the interval, in seconds, before the broker actually shuts down; for immediate shutdown, specify |
|
|
None |
None |
Shut down broker immediately If the broker is part of a high-availability (HA) cluster, another broker will attempt to take over for it. Equivalent to |
|
|
None |
None |
Restart broker |
|
|
None |
None |
Quiesce broker The broker will refuse any new connections; existing connections will continue to be served. |
|
|
None |
None |
Unquiesce broker The broker will again accept new connections. |
|
|
brokerID ( |
None |
Initiate takeover from specified broker The desired broker is designated by its broker identifier (brokerID). |
|
|
propertyName ( |
|
Get value of configuration property The desired property is designated by its name (propertyName) |
|
|
None |
None |
Reset metrics Resets to zero all metrics in monitor MBeans that track cumulative, peak, or average counts. The following attributes are affected: |
|
Service monitor
|
|||
|
Service manager monitor
|
|||
|
Connection manager monitor
|
|||
|
Destination monitor
|
|||
|
Transaction manager monitor
|
Footnote 1 HA clusters only
The broker configuration MBean supports the notification shown in Table 3-3.
The broker monitor MBean is used for monitoring a broker. There is one such MBean for each broker.
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
| Name | Type | Settable? | Description |
|---|---|---|---|
|
|
|
No |
Broker identifier Must be a unique alphanumeric string of no more than n - 13 characters, where n is the maximum table name length allowed by the database. No two running brokers may have the same broker identifier. For brokers using a JDBC-based persistent data store, this string is appended to the names of all database tables to make them unique in the case where more than one broker instance is using the same database. If a database is not used as the persistent data store, the value of this attribute is Note: For high-availability brokers, database table names use the |
|
|
|
No |
Broker version |
|
|
|
No |
Broker instance name |
|
|
|
No |
Port number of Port Mapper |
|
|
|
No |
Current broker resource state:
Note: The threshold values shown are the default thresholds for triggering the various states; these can be changed by setting the broker configuration properties
|
|
|
|
No |
Is broker embedded (started from within another process)? |
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 |
|---|---|---|
|
|
|
Broker has begun shutting down |
|
|
|
Broker has begun quiescing |
|
|
|
Broker has finished quiescing |
|
|
|
Broker has begun taking over persistent data store from another broker |
|
|
|
Broker has finished taking over persistent data store from another broker |
|
|
|
Attempted takeover has failed |
|
|
|
Broker's resource state has changed |
|
|
|
Broker has joined a cluster |
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
| Method | Result Type | Description |
|---|---|---|
|
|
|
Broker identifier |
|
|
|
Broker address, in the form hostName Example:
|
|
|
|
Broker identifier of broker being taken over |
|
|
|
Broker's previous resource state:
Note: The threshold values shown are the default thresholds for triggering the various states; these can be changed by setting the broker configuration properties
|
|
|
|
Broker's new resource state (see |
|
|
|
Broker's current heap memory usage The value returned is an object of class |
Footnote 1 HA clusters only
This section describes the MBeans used for managing connection services:
The service configuration MBean configures a connection service.
The service monitor MBean monitors a connection service.
The service manager configuration MBean manages service configuration MBeans.
The service manager monitor MBean manages service monitor MBeans.
The following subsections describe each of these MBeans in detail.
The service configuration MBean is used for configuring a connection service. There is one such MBean for each service.
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.
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
| Name | Type | Settable? | Description |
|---|---|---|---|
|
|
|
No |
Service name See Table 3-7 for possible values. |
|
|
|
Yes |
Port number ( A value of |
|
|
|
Yes |
Minimum number of threads assigned to service Must be greater than |
|
|
|
Yes |
Maximum number of threads assigned to service Must be greater than or equal to |
|
|
|
No |
Threading model for thread pool management:
|
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.
The service configuration MBean supports the notification shown in Table 3-10.
The service monitor MBean is used for monitoring a connection service. There is one such MBean for each service.
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.
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
| Name | Type | Settable? | Description |
|---|---|---|---|
|
|
|
No |
Service name See Table 3-11 for possible values. |
|
|
|
No |
Port number currently used by service |
|
|
|
No |
Current state See Table 3-13 for possible values. |
|
|
|
No |
String representation of current state: Useful for displaying the state in human-readable form, such as in the Java Monitoring and Management Console ( See Table 3-13 for possible values. |
|
|
|
No |
Current number of connections |
|
|
|
No |
Cumulative number of connections opened since broker started |
|
|
|
No |
Cumulative number of connections rejected since broker started |
|
|
|
No |
Current number of threads actively handling connections |
|
|
|
No |
Current number of message producers |
|
|
|
No |
Current number of message consumers |
|
|
|
No |
Cumulative number of messages received since broker started |
|
|
|
No |
Cumulative number of messages sent since broker started |
|
|
|
No |
Cumulative size in bytes of messages received since broker started |
|
|
|
No |
Cumulative size in bytes of messages sent since broker started |
|
|
|
No |
Cumulative number of packets received since broker started |
|
|
|
No |
Cumulative number of packets sent since broker started |
|
|
|
No |
Cumulative size in bytes of packets received since broker started |
|
|
|
No |
Cumulative size in bytes of packets sent since broker started |
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.
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
| Name | Parameters | Result Type | Description |
|---|---|---|---|
|
|
None |
|
Object names of connection monitor MBeans for all current connections |
|
|
None |
|
Producer identifiers of all current message producers |
|
|
None |
|
Consumer identifiers of all current message consumers |
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
| Name | Utility Constant | Description |
|---|---|---|
|
|
|
Service paused |
|
|
|
Service resumed |
|
|
|
Connection opened |
|
|
|
Connection rejected |
|
|
|
Connection closed |
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
| Method | Result Type | Description |
|---|---|---|
|
|
|
Service name See Table 3-11 for possible values. |
Each broker has a single service manager configuration MBean, used for managing all of the broker's service configuration MBeans.
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.
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.
Each broker has a single service manager monitor MBean, used for managing all of the broker's service monitor MBeans.
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
| Name | Type | Settable? | Description |
|---|---|---|---|
|
|
|
No |
Number of connection services |
|
|
|
No |
Total current number of threads actively handling connections for all services |
|
|
|
No |
Total cumulative number of messages received by all services since broker started |
|
|
|
No |
Total cumulative number of messages sent by all services since broker started |
|
|
|
No |
Total cumulative size in bytes of messages received by all services since broker started |
|
|
|
No |
Total cumulative size in bytes of messages sent by all services since broker started |
|
|
|
No |
Total cumulative number of packets received by all services since broker started |
|
|
|
No |
Total cumulative number of packets sent by all services since broker started |
|
|
|
No |
Total cumulative size in bytes of packets received by all services since broker started |
|
|
|
No |
Total cumulative size in bytes of packets sent by all services since broker started |
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.
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
| Name | Utility Constant | Description |
|---|---|---|
|
|
|
Service paused |
|
|
|
Service resumed |
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
| Method | Result Type | Description |
|---|---|---|
|
|
|
Service name See Table 3-11 for possible values. |
This section describes the MBeans used for managing connections:
The connection configuration MBean configures a connection.
The connection monitor MBean monitors a connection.
The connection manager configuration MBean manages connection configuration MBeans.
The connection manager monitor MBean manages connection monitor MBeans.
The following subsections describe each of these MBeans in detail.
The connection configuration MBean is used for configuring a connection. There is one such MBean for each connection.
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:
com.sun.messaging.jms.server:type=Connection,subtype=Config, id=7853717387765338368
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.
The connection monitor MBean is used for monitoring a connection. There is one such MBean for each connection.
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:
com.sun.messaging.jms.server:type=Connection,subtype=Monitor, id=7853717387765338368
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
| Name | Type | Settable? | Description |
|---|---|---|---|
|
|
|
No |
Connection identifier |
|
|
|
No |
Host from which connection was made |
|
|
|
No |
Port number |
|
|
|
No |
Connection service name |
|
|
|
No |
User name |
|
|
|
No |
Client identifier |
|
|
|
No |
String describing client platform |
|
|
|
No |
Current number of associated message producers |
|
|
|
No |
Current number of associated message consumers |
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
| Name | Parameters | Result Type | Description |
|---|---|---|---|
|
|
None |
|
Object name of service monitor MBean for associated connection service |
|
|
None |
|
Object names of destination monitor MBeans for all associated temporary destinations |
|
|
None |
|
Producer identifiers of all associated message producers |
|
|
None |
|
Consumer identifiers of all associated message consumers |
Each broker has a single connection manager configuration MBean, used for managing all of the broker's connection configuration MBeans.
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.
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
| Name | Parameters | Result Type | Description |
|---|---|---|---|
|
|
None |
|
Object names of connection configuration MBeans for all current connections |
|
|
connectionID ( |
None |
Destroy connection The desired connection is designated by its connection identifier (connectionID). |
Each broker has a single connection manager monitor MBean, used for managing all of the broker's connection monitor MBeans.
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
| Name | Type | Settable? | Description |
|---|---|---|---|
|
|
|
No |
Current number of connections |
|
|
|
No |
Cumulative number of connections opened since broker started |
|
|
|
No |
Cumulative number of connections rejected since broker started |
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.
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
| Name | Utility Constant | Description |
|---|---|---|
|
|
|
Connection opened |
|
|
|
Connection rejected |
|
|
|
Connection closed |
Table 3-31 shows the methods defined in class ConnectionNotification for obtaining details about a connection manager monitor notification.
This section describes the MBeans used for managing destinations:
The destination configuration MBean configures a destination.
The destination monitor MBean monitors a destination.
The destination manager configuration MBean manages destination configuration MBeans.
The destination manager monitor MBean manages destination monitor MBeans.
The following subsections describe each of these MBeans in detail.
The destination configuration MBean is used for configuring a destination. There is one such MBean for each destination.
The destination configuration MBean has an object name of the following form:
com.sun.messaging.jms.server:type=Destination,subtype=Config, desttype=destinationType,name=destinationName
where destinationType is one of the destination types shown in Table 3-33 and destinationName is the name of the destination. For example:
com.sun.messaging.jms.server:type=Destination,subtype=Config,desttype=t, name="Dest"
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
| Name | Type | Settable? | Description |
|---|---|---|---|
|
|
|
No |
Destination name |
|
|
|
No |
Destination type See Table 3-33 for possible values. |
|
|
|
Yes |
Maximum number of unconsumed messages A value of |
|
|
|
Yes |
Maximum size, in bytes, of any single message Rejection of a persistent message is reported to the producing client with an exception; no notice is sent for nonpersistent messages. A value of |
|
|
|
Yes |
Maximum total memory, in bytes, for unconsumed messages |
|
|
|
Yes |
Broker behavior when memory-limit threshold reached See Table 3-34 for possible values. If the value is |
|
|
|
Yes |
Maximum number of associated message producers When this limit is reached, no new producers can be created. A value of |
|
|
|
Yes |
Maximum number of associated active message consumers in load-balanced delivery A value of |
|
|
|
Yes |
Maximum number of associated backup message consumers in load-balanced delivery A value of |
|
|
|
Yes |
Maximum number of messages delivered to consumer in a single batch In load-balanced queue delivery, this is the initial number of queued messages routed to active consumers before load balancing begins. A destination consumer can override this limit by specifying a lower value on a connection. A value of |
|
|
|
No |
Local delivery only? This property applies only to destinations in broker clusters, and cannot be changed once the destination has been created. If |
|
|
|
Yes |
Local delivery preferred? This property applies only to load-balanced delivery in broker clusters. If |
|
|
|
Yes |
Send dead messages to dead message queue? If |
|
|
|
Yes |
XML schema validation is enabled? If set to |
|
|
|
Yes |
Space separated list of XML schema document (XSD) URI strings The URIs point to the location of one or more XSDs to use for XML schema validation, if enabled. Use double quotes around this value if multiple URIs are specified. Example: " If this property is not set or null and XML validation is enabled, XML validation is performed using a DTD specified in the XML document. |
|
|
|
Yes |
Reload XML schema on failure enabled? If set to false or not set, then the schema is not reloaded if validation fails. |
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
| Value | Utility Constant | Meaning |
|---|---|---|
|
|
|
Queue (point-to-point) destination |
|
|
|
Topic (publish/subscribe) destination |
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
| Value | Utility Constant | Meaning |
|---|---|---|
|
|
|
Slow down producers |
|
|
|
Throw out oldest messages |
|
|
|
Throw out lowest-priority messages according to age; no notice to producing client |
|
|
|
Reject newest messages; notify producing client with an exception only if message is persistent |
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
| Name | Parameters | Result Type | Description |
|---|---|---|---|
|
|
pauseType ( |
None |
Pause message delivery See Table 3-36 for possible values of pauseType. |
|
|
None |
None |
Pause all message delivery Equivalent to |
|
|
None |
None |
Resume message delivery |
|
|
None |
None |
Purge all messages |
|
|
None |
None |
Compact persistent data store Note: Only a paused destination can be compacted. |
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.
The destination configuration MBean supports the notification shown in Table 3-37.
The destination monitor MBean is used for monitoring a destination. There is one such MBean for each destination.
The destination monitor MBean has an object name of the following form:
com.sun.messaging.jms.server:type=Destination,subtype=Monitor, desttype=destinationType,name=destinationName
where destinationType is one of the destination types shown in Table 3-39 and destinationName is the name of the destination. For example:
com.sun.messaging.jms.server:type=Destination,subtype=Monitor,desttype=t, name="Dest"
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
| Name | Type | Settable? | Description |
|---|---|---|---|
|
|
|
No |
Destination name |
|
|
|
No |
Destination type See Table 3-39 for possible values. |
|
|
|
No |
Administrator-created destination? |
|
|
|
No |
Temporary destination? |
|
|
|
No |
Connection identifier |
|
|
|
No |
Current state See Table 3-40 for possible values. |
|
|
|
No |
String representation of current state: Useful for displaying the state in human-readable form, such as in the Java Monitoring and Management Console ( See Table 3-40 for possible values. |
|
|
|
No |
Current number of associated message producers |
|
|
|
No |
Current number of associated message consumers For queue destinations, this attribute includes both active and backup consumers. For topic destinations, it includes both nondurable and (active and inactive) durable subscribers and is equivalent to |
|
|
|
No |
Current number of wildcard message producers associated with the destination For topic destinations only. |
|
|
|
No |
Current number of wildcard message consumers associated with the destination For topic destinations only. |
|
|
|
No |
Current number of wildcard message producers and wildcard message consumers associated with the destination For topic destinations only. |
|
|
|
No |
Peak number of associated message consumers since broker started For queue destinations, this attribute includes both active and backup consumers. For topic destinations, it includes both nondurable and (active and inactive) durable subscribers and is equivalent to |
|
|
|
No |
Average number of associated message consumers since broker started For queue destinations, this attribute includes both active and backup consumers. For topic destinations, it includes both nondurable and (active and inactive) durable subscribers and is equivalent to |
|
|
|
No |
Current number of associated active message consumers For topic destinations, this attribute includes both nondurable and (active and inactive) durable subscribers and is equivalent to |
|
|
|
No |
Peak number of associated active message consumers since broker started For topic destinations, this attribute includes both nondurable and (active and inactive) durable subscribers and is equivalent to |
|
|
|
No |
Average number of associated active message consumers since broker started For topic destinations, this attribute includes both nondurable and (active and inactive) durable subscribers and is equivalent to |
|
|
|
No |
Current number of associated backup message consumers |
|
|
|
No |
Peak number of associated backup message consumers since broker started |
|
|
|
No |
Average number of associated backup message consumers since broker started |
|
|
|
No |
Current number of messages stored in memory and persistent store Does not include messages held in transactions. |
|
|
|
No |
Current number of messages stored in memory and persistent store that were produced to a remote broker in a cluster. This number does not include messages included in transactions. |
|
|
|
No |
Current number of messages being held in memory and persistent store pending acknowledgment |
|
|
|
No |
Current number of messages being held in memory and persistent store in uncommitted transactions |
|
|
|
No |
JMS Message ID of the next message to be delivered to any consumer |
|
|
|
No |
Peak number of messages stored in memory and persistent store since broker started |
|
|
|
No |
Average number of messages stored in memory and persistent store since broker started |
|
|
|
No |
Cumulative number of messages received since broker started |
|
|
|
No |
Cumulative number of messages sent since broker started |
|
|
|
No |
Cumulative size in bytes of messages received since broker started |
|
|
|
No |
Cumulative size in bytes of messages sent since broker started |
|
|
|
No |
Size in bytes of largest single message received since broker started |
|
|
|
No |
Current total size in bytes of messages stored in memory and persistent store Does not include messages held in transactions. |
|
|
|
No |
Current total size in bytes of messages stored in memory and persistent store that were produced to a remote broker in a cluster. This value does not include messages included in transactions. |
|
|
|
No |
Current total size in bytes of messages being held in memory and persistent store in uncommitted transactions |
|
|
|
No |
Peak total size in bytes of messages stored in memory and persistent store since broker started |
|
|
|
No |
Average total size in bytes of messages stored in memory and persistent store since broker started |
|
|
|
No |
Amount of disk space, in bytes, reserved for destination |
|
|
|
No |
Amount of disk space, in bytes, currently in use by destination |
|
|
|
No |
Ratio of disk space currently in use to disk space reserved for destination |
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
| Value | Utility Constant | Meaning |
|---|---|---|
|
|
|
Queue (point-to-point) destination |
|
|
|
Topic (publish/subscribe) destination |
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
| Value | Utility Constant | String Representation | Meaning |
|---|---|---|---|
|
|
|
|
Destination running |
|
|
|
|
Message consumers paused |
|
|
|
|
Message producers paused |
|
|
|
|
Destination paused |
|
|
|
|
Destination state unknown |
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
| Name | Parameters | Result Type | Description |
|---|---|---|---|
|
|
None |
|
Object name of connection monitor MBean for connection |
|
|
None |
|
Producer identifiers of all current associated message producers |
|
|
None |
|
Consumer identifiers of all current associated message consumers For queue destinations, this operation returns both active and backup consumers. For topic destinations, it returns both nondurable and (active and inactive) durable subscribers. |
|
|
None |
|
Consumer identifiers of all current associated active message consumers For topic destinations, this operation returns both nondurable and (active and inactive) durable subscribers. |
|
|
None |
|
Consumer identifiers of all current associated backup message consumers |
|
|
none |
|
Wildcard strings used by current consumers associated with the destination For topic destinations only. |
|
|
none |
|
Wildcard strings used by current producers associated with the destination For topic destinations only. |
|
|
none |
|
Wildcard strings used by current consumers and producers associated with the destination For topic destinations only. |
|
|
wildcard-String |
|
Number of current consumers associated with the destination that are using the specified wildcard string For topic destinations only. |
|
|
wildcard-String |
|
Number of current producers associated with the destination that are using the specified wildcard string For topic destinations only. |
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
| Name | Utility Constant | Description |
|---|---|---|
|
|
|
Destination paused |
|
|
|
Destination resumed |
|
|
|
Destination compacted |
|
|
|
Destination purged |
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
| Method | Result Type | Description |
|---|---|---|
|
|
|
Destination name |
|
|
|
Destination type See Table 3-39 for possible values. |
|
|
|
Administrator-created destination? |
|
|
|
Pause type See Table 3-36 for possible values. |
Each broker has a single destination manager configuration MBean, used for managing all of the broker's destination configuration MBeans.
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
| Name | Type | Settable? | Description |
|---|---|---|---|
|
|
|
Yes |
Allow auto-creation of queue destinations? |
|
|
|
Yes |
Allow auto-creation of topic destinations? |
|
|
|
No |
Current total number of destinations |
|
|
|
Yes |
Maximum total number of unconsumed messages A value of -1 denotes an unlimited number of messages. |
|
|
|
Yes |
Maximum size, in bytes, of any single message A value of -1 denotes an unlimited message size. |
|
|
|
Yes |
Maximum total memory, in bytes, for unconsumed messages A value of -1 denotes an unlimited number of bytes. |
|
|
|
Yes |
Maximum total number of active message consumers in load-balanced delivery A value of -1 denotes an unlimited number of consumers. |
|
|
|
Yes |
Maximum total number of backup message consumers in load-balanced delivery A value of -1 denotes an unlimited number of consumers. |
|
|
|
Yes |
Remove message body before storing in dead message queue? If true, only the message header and property data will be saved. |
|
|
|
Yes |
Log information about dead messages? If
|
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
| Name | Parameters | Result Type | Description |
|---|---|---|---|
|
|
None |
|
Object names of destination configuration MBeans for all current destinations |
|
|
destinationType ( destinationName ( destinationAttributes ( |
None |
Create destination with specified type, name, and attributes The destinationType and destinationName parameters are required, but destinationAttributes may be null. See Table 3-46 for possible values of destinationType. The destinationAttributes list may include any of the attributes listed in Table 3-32 except |
|
|
destinationType ( destinationName ( |
None |
Create destination with specified type and name Equivalent to See Table 3-46 for possible values of destinationType. |
|
|
destinationType ( destinationName ( |
None |
Destroy destination See Table 3-46 for possible values of destinationType. |
|
|
pauseType ( |
None |
Pause message delivery for all destinations See Table 3-47 for possible values of pauseType. |
|
|
None |
None |
Pause all message delivery for all destinations Equivalent to |
|
|
None |
None |
Resume message delivery for all destinations |
|
|
None |
None |
Compact all destinations Note: Only paused destinations can be compacted. |
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
| Value | Utility Constant | Meaning |
|---|---|---|
|
|
|
Queue (point-to-point) destination |
|
|
|
Topic (publish/subscribe) destination |
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.
The destination manager configuration MBean supports the notification shown in Table 3-48.
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
| Name | Type | Settable? | Description |
|---|---|---|---|
|
|
|
No |
Current total number of destinations |
|
|
|
No |
Current total number of messages stored in memory and persistent store for all destinations Does not include messages held in transactions. |
|
|
|
No |
Current total size in bytes of messages stored in memory and persistent store for all destinations Does not include messages held in transactions. |
|
|
|
No |
Current number of messages stored in memory and persistent store for dead message queue |
|
|
|
No |
Current total size in bytes of messages stored in memory and persistent store for dead message queue |
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.
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 |
|---|---|---|
|
|
|
Destination name |
|
|
|
Destination type See Table 3-46 for possible values. |
|
|
|
Administrator-created destination? |
|
|
|
Pause type See Table 3-47 for possible values. |
This section describes the MBeans used for managing message producers:
The producer manager configuration MBean configures message producers.
The producer manager monitor MBean monitors message producers.
The following subsections describe each of these MBeans in detail.
Note:
Notice that there are no resource MBeans associated with individual message producers; rather, all producers are managed through the broker's global producer manager configuration and producer manager monitor MBeans.
Each broker has a single producer manager configuration MBean, used for configuring all of the broker's message producers.
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.
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.
Each broker has a single producer manager monitor MBean, used for monitoring all of the broker's message producers.
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.
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
| Name | Parameters | Result Type | Description |
|---|---|---|---|
|
|
None |
|
Producer identifiers of all current message producers |
|
|
producerID ( |
|
Descriptive information about message producer The desired producer is designated by its producer identifier (producerID). The value returned is a JMX |
|
|
None |
|
Descriptive information about all current message producers The value returned is an array of JMX |
|
|
None |
|
Wildcard strings used by current producers associated with the broker |
|
|
wildcard-String |
|
Number of current producers associated with the broker that are using the specified wildcard string |
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
| Name | Value Type | Description |
|---|---|---|
|
|
|
Producer identifier |
|
|
|
Name of associated connection service |
|
|
|
Connection identifier of associated connection |
|
|
|
Connection's host name |
|
|
|
Connection's user name |
|
|
|
Name of associated destination |
|
|
|
Destination names that match wildcards used by wildcard producers For topic destinations only. |
|
|
|
Wildcard producer? For topic destinations only. |
|
|
|
Type of associated destination See Table 3-58 for possible values. |
|
|
|
Message delivery paused? |
|
|
|
Number of messages sent |
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.
This section describes the MBeans used for managing message consumers:
The consumer manager configuration MBean configures message consumers.
The consumer manager monitor MBean monitors message consumers.
The following subsections describe each of these MBeans in detail.
Note:
Notice that there are no resource MBeans associated with individual message consumers; rather, all consumers are managed through the broker's global consumer manager configuration and consumer manager monitor MBeans.
Each broker has a single consumer manager configuration MBean, used for configuring all of the broker's message consumers.
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.
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
| Name | Parameters | Result Type | Description |
|---|---|---|---|
|
|
None |
|
Consumer identifiers of all current message consumers |
|
|
consumerID ( |
None |
Purge all messages The desired subscriber is designated by its consumer identifier (consumerID). The subscriber itself is not destroyed. |
Footnote 1 Durable topic subscribers only
Each broker has a single consumer manager monitor MBean, used for monitoring all of the broker's message consumers.
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.
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
| Name | Parameters | Result Type | Description |
|---|---|---|---|
|
|
None |
|
Consumer identifiers of all current message consumers |
|
|
consumerID ( |
|
Descriptive information about message consumer The desired consumer is designated by its consumer identifier (consumerID). The value returned is a JMX |
|
|
None |
|
Descriptive information about all current message consumers The value returned is an array of JMX |
|
|
none |
|
Wildcard strings used by current consumers associated with the broker |
|
|
wildcard-String |
|
Number of current consumers associated with the broker that are using the specified wildcard string |
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
| Name | Value Type | Description |
|---|---|---|
|
|
|
Consumer identifier |
|
|
|
Message selector |
|
|
|
Name of associated connection service |
|
|
|
Connection identifier of associated connection |
|
|
|
Connection's host name |
|
|
|
Connection's user name |
|
|
|
Name of associated destination |
|
|
|
Destination names that match wildcards used by wildcard consumers For topic destinations only. |
|
|
|
Wildcard consumer? For topic destinations only. |
|
|
|
Type of associated destination See Table 3-64 for possible values. |
|
|
|
Acknowledgment mode of associated session See Table 3-65 for possible values. |
|
|
|
String representation of acknowledgment mode Useful for displaying the acknowledgment mode in human-readable form, such as in the Java Monitoring and Management Console ( See Table 3-65 for possible values. |
|
|
|
Durable topic subscriber? |
|
|
|
Subscription name |
|
|
|
Client identifier |
|
|
|
Subscriber active? |
|
|
|
Message delivery paused? |
|
|
|
Cumulative number of messages that have been dispatched to consumer (includes messages that have been delivered and those waiting to be delivered) |
|
|
|
Current number of messages that have been dispatched to consumer and are being held in broker memory and persistent store (includes messages that have been delivered and those waiting to be delivered) |
|
|
|
Current number of messages that have been delivered to consumer and are being held in broker memory and persistent store pending acknowledgment |
|
|
|
JMS Message ID of the next message to be delivered to consumer |
|
|
|
Time of last acknowledgment, in standard Java format (milliseconds since January 1, 1970, 00:00:00 UTC) |
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
| Value | Utility Constant | Meaning |
|---|---|---|
|
|
|
Queue (point-to-point) destination |
|
|
|
Topic (publish/subscribe) destination |
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 javax.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
| Value | Utility Constant | String Representation | Meaning |
|---|---|---|---|
|
|
|
|
Auto-acknowledge mode |
|
|
|
|
Client-acknowledge mode |
|
|
|
|
Dups-OK-acknowledge mode |
|
|
|
|
No-acknowledge mode |
|
|
|
|
Session is transacted (acknowledgment mode ignored) |
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.
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
| Name | Parameters | Result Type | Description |
|---|---|---|---|
|
|
None |
|
Transaction identifiers of all current open transactions |
|
|
transactionID ( |
None |
Commit transaction The desired transaction is designated by its transaction identifier (transactionID). |
|
|
transactionID ( |
None |
Roll back transaction The desired transaction is designated by its transaction identifier (transactionID). |
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 |
|---|---|---|---|
|
|
|
No |
Current number of open transactions |
|
|
|
No |
Cumulative number of transactions committed since broker started |
|
|
|
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 |
|
Transaction identifiers of all current open transactions |
|
|
transactionID ( |
|
Descriptive information about transaction The desired transaction is designated by its transaction identifier (transactionID). The value returned is a JMX |
|
|
None |
|
Descriptive information about all current open transactions The value returned is an array of JMX |
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 |
|---|---|---|
|
|
|
Transaction identifier |
|
|
|
Distributed transaction identifier (XID) |
|
|
|
User name |
|
|
|
Client identifier |
|
|
|
Connection string |
|
|
|
Time created, in standard Java format (milliseconds since January 1, 1970, 00:00:00 UTC) |
|
|
|
Current state See Table 3-71 for possible values. |
|
|
|
String representation of current state Useful for displaying the state in human-readable form, such as in the Java Monitoring and Management Console ( See Table 3-71 for possible values. |
|
|
|
Number of messages |
|
|
|
Number of acknowledgments |
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
| Value | Utility Constant | String Representation | Meaning |
|---|---|---|---|
|
|
|
|
Transaction created |
|
|
|
|
Transaction started |
|
|
|
|
Transaction has failed |
|
|
|
|
Transaction incomplete |
|
|
|
|
Transaction complete |
|
|
|
|
Transaction in prepared stateFoot 1 |
|
|
|
|
Transaction committed |
|
|
|
|
Transaction rolled back |
|
|
|
|
Transaction has timed out |
|
|
|
|
Transaction state unknown |
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
| Name | Utility Constant | Description |
|---|---|---|
|
|
|
Transaction has entered prepared state |
|
|
|
Transaction committed |
|
|
|
Transaction rolled back |
Footnote 1 Distributed transactions only
Table 3-73 shows the method defined in class TransactionNotification for obtaining details about a transaction manager monitor notification.
This section describes the MBeans used for managing broker clusters:
The cluster configuration MBean configures a broker's cluster-related properties.
The cluster monitor MBean monitors the brokers in a cluster.
The following subsections describe each of these MBeans in detail.
The cluster configuration MBean is used for configuring a broker's cluster-related properties. There is one such MBean for each broker.
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
| Name | Type | Settable? | Description |
|---|---|---|---|
|
|
|
No |
High-availability (HA) cluster? |
|
|
|
No |
Cluster identifier Must be a unique alphanumeric string of no more than n - 13 characters, where n is the maximum table name length allowed by the database. No two running clusters may have the same cluster identifier. This string is appended to the names of all database tables in the cluster's shared persistent store. Note: For brokers belonging to an HA cluster, this attribute is used in database table names in place of |
|
|
|
Yes |
URL of cluster configuration file |
|
|
|
No |
Descriptive information about local broker The value returned is a JMX |
|
|
|
No |
Descriptive information about master broker The value returned is a JMX |
|
|
|
No |
Does conventional cluster use a shared JDBC data store instead of a master broker for the cluster configuration change record? |
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
| Name | Parameters | Result Type | Description |
|---|---|---|---|
|
|
None |
|
Addresses of brokers in cluster Each address specifies the host name and Port Mapper port number of a broker in the cluster, in the form hostName Example:
For conventional clusters, the list includes all brokers specified by the broker property |
|
|
None |
|
Broker identifiers of brokers in cluster The list includes all active and inactive brokers in the cluster table stored in the HA database. |
|
|
brokerAddress ( |
|
Descriptive information about broker The desired broker is designated by its host name and Port Mapper port number (brokerAddress), in the form hostName |
|
|
brokerID ( |
|
Descriptive information about broker The desired broker is designated by its broker identifier (brokerID). The value returned is a JMX |
|
|
None |
|
Descriptive information about all brokers in cluster The value returned is an array of JMX For conventional clusters, the array includes all brokers specified by the broker property |
|
|
None |
None |
Reload cluster configuration file |
|
|
oldMasterBroker ( |
|
Specify a change of master broker from oldMasterBroker to newMasterBroker, where both arguments are in imq.cluster.masterbroker format (host:port). The value returned is a JMX This operation can only be performed on the broker that is the current master broker. If it is performed on any other broker it will have no effect and the This operation must not be performed on a broker whose lifecycle is being managed by GlassFish Server. In this case GlassFish Server tools must be used instead. |
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
| Key | Value Type | Description |
|---|---|---|
|
|
|
Broker address, in the form hostName Example:
|
|
|
|
Broker identifier |
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
| Key | Value Type | Description |
|---|---|---|
|
|
|
Whether an error occurred when performing the |
|
|
|
A status code set when an error occurred. The |
|
|
|
An error message set when an error occurs. The possible errors, and the actions that should be taken to resolve them, are the same as for the |
The cluster configuration MBean supports the notification shown in Table 3-78.
The cluster monitor MBean is used for monitoring the brokers in a cluster. There is one such MBean for each broker.
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
| Name | Type | Settable? | Description |
|---|---|---|---|
|
|
|
No |
High-availability (HA) cluster? |
|
|
|
No |
Cluster identifier Must be a unique alphanumeric string of no more than n - 13 characters, where n is the maximum table name length allowed by the database. No two running clusters may have the same cluster identifier. This string is appended to the names of all database tables in the cluster's shared persistent store. Note: For brokers belonging to an HA cluster, this attribute is used in database table names in place of |
|
|
|
Yes |
URL of cluster configuration file |
|
|
|
No |
Descriptive information about local broker The value returned is a JMX |
|
|
|
No |
Descriptive information about master broker The value returned is a JMX |
|
|
|
No |
Does conventional cluster use a shared JDBC data store instead of a master broker for the cluster configuration change record? |
Footnote 1 HA clusters only
Footnote 2 Conventional clusters only
The cluster monitor MBean supports the operations shown in Table 3-80. The names of these operations are defined as static constants in the utility class ClusterOperations.
Table 3-80 Cluster Monitor Operations
| Name | Parameters | Result Type | Description |
|---|---|---|---|
|
|
None |
|
Addresses of brokers in cluster Each address specifies the host name and Port Mapper port number of a broker in the cluster, in the form hostName Example:
For conventional clusters, the list includes all brokers specified by the broker property |
|
|
None |
|
Broker identifiers of brokers in cluster The list includes all active and inactive brokers in the cluster table stored in the HA database. |
|
|
brokerAddress ( |
|
Descriptive information about broker The desired broker is designated by its host name and Port Mapper port number (brokerAddress), in the form hostName |
|
|
brokerID ( |
|
Descriptive information about broker The desired broker is designated by its broker identifier (brokerID). The value returned is a JMX |
|
|
None |
|
Descriptive information about all brokers in cluster The value returned is an array of JMX For conventional clusters, the array includes all brokers specified by the broker property |
Footnote 1 HA 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-81 are defined as static constants in the utility class BrokerClusterInfo for use with these objects.
Table 3-81 Lookup Keys for Cluster Monitor Information
| Key | Value Type | Description |
|---|---|---|
|
|
|
Broker address, in the form hostName Example:
|
|
|
|
Broker identifier |
|
|
|
Current state of broker See Table 3-82 for possible values. |
|
|
|
String representation of current broker state Useful for displaying the state in human-readable form, such as in the Java Monitoring and Management Console ( See Table 3-82 for possible values. |
|
|
|
Broker identifier of broker that has taken over this broker's persistent data store |
|
|
|
Current number of messages stored in memory and persistent store |
|
|
|
Time of last status update, in standard Java format (milliseconds since January 1, 1970, 00:00:00 UTC) Used to determine whether a broker is running. The interval at which a broker updates its status can be configured with the broker property |
Footnote 1 HA clusters only
Table 3-82 shows the possible values returned for the lookup keys State and StateLabel. These values are defined as static constants in the utility class BrokerState.
Table 3-82 Broker State Values
| Value | Utility Constant | String Representation | Meaning |
|---|---|---|---|
|
|
|
|
Broker is operating |
|
|
|
|
Broker has begun taking over persistent data store from another broker |
|
|
|
|
Broker has finished taking over persistent data store from another broker |
|
|
|
|
Attempted takeover has failed |
|
|
|
|
Broker has begun quiescing |
|
|
|
|
Broker has finished quiescing |
|
|
|
|
Broker has begun shutting down |
|
|
|
|
Broker is down |
|
|
|
|
Broker state unknown |
The cluster monitor MBean supports the notifications shown in Table 3-83. These notifications are instances of the Message Queue JMX classes ClusterNotification and BrokerNotification, and their names are defined as static constants in those classes.
Table 3-83 Cluster Monitor Notifications
| Name | Utility Constant | Description |
|---|---|---|
|
|
|
A broker has joined the cluster |
|
|
|
A broker in the cluster has shut down or crashed |
|
|
|
A broker has begun taking over persistent data store from another broker |
|
|
|
A broker has finished taking over persistent data store from another broker |
|
|
|
An attempted takeover has failed |
Footnote 1 HA clusters only
Table 3-84 shows the methods defined in class ClusterNotification for obtaining details about a cluster monitor notification. See Table 3-6 for the corresponding methods of class BrokerNotification.
Table 3-84 Data Retrieval Methods for Cluster Monitor Notifications
| Method | Result Type | Description |
|---|---|---|
|
|
|
High-availability (HA) cluster? |
|
|
|
Cluster identifier |
|
|
|
Broker identifier of affected broker |
|
|
|
Address of affected broker, in the form hostName Example:
|
|
|
|
Master broker affected? |
Footnote 1 Conventional clusters only
This section describes the MBeans used for logging Message Queue operations:
The log configuration MBean configures Message Queue logging.
The log monitor MBean monitors Message Queue logging.
The following subsections describe each of these MBeans in detail.
Each broker has a single log configuration MBean, used for configuring Message Queue logging.
The log configuration MBean has the following object name:
com.sun.messaging.jms.server:type=Log,subtype=Config
A string representing this object name is defined as a static constant LOG_CONFIG_MBEAN_NAME in the utility class MQObjectName.
The log configuration MBean has the attributes shown in Table 3-85. The names of these attributes are defined as static constants in the utility class LogAttributes.
Table 3-85 Log Configuration Attributes
| Name | Type | Settable? | Description |
|---|---|---|---|
|
|
|
Yes |
Logging level Specifies the categories of logging information that can be written to an output channel. See Table 3-86 for possible values. |
|
|
|
Yes |
File length, in bytes, at which output rolls over to a new log file A value of |
|
|
|
Yes |
Age of file, in seconds, at which output rolls over to a new log file A value of |
Table 3-86 shows the possible values for the Level attribute. Each level includes those above it (for example, WARNING includes ERROR). These values are defined as static constants in the utility class LogLevel.
The log configuration MBean supports the notification shown in Table 3-87.
Each broker has a single log monitor MBean, used for monitoring Message Queue logging.
The log monitor MBean has the following object name:
com.sun.messaging.jms.server:type=Log,subtype=Monitor
A string representing this object name is defined as a static constant LOG_MONITOR_MBEAN_NAME in the utility class MQObjectName.
The log monitor MBean supports the notifications shown in Table 3-88. These notifications are instances of the Message Queue JMX class LogNotification, and their names are defined as static utility constants in that class.
Note:
A notification listener registered for a particular logging level will receive notifications only for that level and not for those above or below it: for example, a listener registered for the notification mq.log.level.WARNING will be notified only of WARNING messages and not ERROR or INFO. To receive notifications for more than one logging level, the listener must be explicitly registered for each level separately.
Table 3-88 Log Monitor Notifications
| Name | Utility Constant | Description |
|---|---|---|
|
|
|
Error message logged |
|
|
|
Warning message logged |
|
|
|
Informational message logged |
Table 3-89 shows the methods defined in class LogNotification for obtaining details about a log monitor notification.
Table 3-89 Data Retrieval Methods for Log Monitor Notifications
| Method | Result Type | Description |
|---|---|---|
|
|
|
Logging level of logged message See Table 3-86 for possible values. |
|
|
|
Body of logged message |
This section describes the MBean used for monitoring the Java Virtual Machine (JVM). The following subsection describes this MBean in detail.
Each broker has a single JVM monitor MBean, used for monitoring the Java Virtual Machine (JVM).
Note:
This MBean is useful only with the Java Development Kit (JDK ) version 1.4 or lower. JDK version 1.5 includes built-in MBeans that provide more detailed information on the state of the JVM.
The JVM monitor MBean has the following object name:
com.sun.messaging.jms.server:type=JVM,subtype=Monitor
A string representing this object name is defined as a static constant JVM_MONITOR_MBEAN_NAME in the utility class MQObjectName.
The JVM monitor MBean has the attributes shown in Table 3-90. The names of these attributes are defined as static constants in the utility class JVMAttributes.
Table 3-90 JVM Monitor Attributes
| Name | Type | Settable? | Description |
|---|---|---|---|
|
|
|
No |
Current total memory, in bytes |
|
|
|
No |
Initial heap size at JVM startup, in bytes |
|
|
|
No |
Amount of memory currently available for use, in bytes |
|
|
|
No |
Maximum allowable heap size, in bytes Any memory allocation attempt that would exceed this limit will cause an |
|
 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
