| 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
Consumer Manager Configuration
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.
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 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.
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
|
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.
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
|
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
|
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
|
|