Monitoring Queues Monitoring Topics Monitoring Durable Subscribers for Topics

Monitoring JMS Statistics and Managing Messages 8-3

8.1.1.4 Monitoring Active JMS Session Pools

You can monitor statistics on all the active JMS session pools defined for a JMS server. Session pools enable an application to process messages concurrently. For more information on the runtime statistics provided for active JMS session pools, see JMS Server: Monitoring: Active Session Pools in the Oracle WebLogic Server Administration Console Help.

8.1.2 Monitoring Queues

You can monitor statistics on queue resources in JMS modules via the Administration Console or through the JMSDestinationRuntimeMBean. A JMS queue defines a point-to-point destination type for a JMS server. Queues are used for synchronous peer communications. A message delivered to a queue will be distributed to one consumer. For more information on using the Administration Console to monitor queue resources, see Monitor queues in JMS system modules in the Oracle WebLogic Server Administration Console Help. You can also use the Administration Console to manage messages on queues, as described in Section 8.2, Managing JMS Messages.

8.1.3 Monitoring Topics

You can monitor statistics on topic resources in JMS modules via the Administration Console or through the JMSDestinationRuntimeMBean. A JMS topic identifies a publishsubscribe destination type for a JMS server. Topics are used for asynchronous peer communications. A message delivered to a topic will be distributed to all topic consumers. For more information on using the Administration Console to monitor topic resources, see Monitor topics in JMS system modules in theOracle WebLogic Server Administration Console Help.

8.1.4 Monitoring Durable Subscribers for Topics

You can monitor statistics on all the durable subscribers that are running on your JMS topics via the Administration Console or through the JMSDurableSubscriberRuntimeMBean. Durable subscribers allow you to assign a name to a topic subscriber and associate it with a user or application. WebLogic stores durable subscribers in a persistent file-base store or JDBC-accessible database until the message has been delivered to the subscribers or has expired, even if those subscribers are not active at the time that the message is delivered. You can use the Administration Console to manage durable subscribers running on topics, as described in Section 8.2, Managing JMS Messages.

8.1.5 Monitoring Uniform Distributed Queues