Monitoring Uniform Distributed Queues Monitoring Uniform Distributed Topics Monitoring Pooled JMS Connections

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

You can monitor statistics on uniform distributed queue resources in JMS modules via the Administration Console or through the JMSDestinationRuntimeMBean. A distributed queue resource is a single set of queues that are accessible as a single, logical destination to a client for example, a distributed topic has its own JNDI name. The members of the unit are usually distributed across multiple servers within a cluster, with each member belonging to a separate JMS server. 8-4 Configuring and Managing JMS for Oracle WebLogic Server For more information on using the Administration Console to monitor uniform distributed queue resources, see Uniform distributed queues - monitor statistics in the Oracle WebLogic Server Administration Console Help. You can also use the Administration Console to manage messages on distributed queues, as described in Section 8.2, Managing JMS Messages.

8.1.6 Monitoring Uniform Distributed Topics

You can monitor statistics on uniform distributed topic resources in JMS modules via the Administration Console or through the JMSDestinationRuntimeMBean. A distributed topic resource is a single set of topics that are accessible as a single, logical destination to a client for example, a distributed topic has its own JNDI name. The members of the unit are usually distributed across multiple servers within a cluster, with each member belonging to a separate JMS server. For more information on using the Administration Console to monitor uniform distributed topic resources, see Uniform distributed queues - monitor statistics in the Oracle WebLogic Server Administration Console Help.

8.1.7 Monitoring Pooled JMS Connections

You can monitor statistics on all the active pooled JMS connections on your server. A pooled JMS connection is a session pool used by EJBs and servlets that use a resource-reference element in their EJB or servlet deployment descriptor to define their JMS connection factories. For more information, see JMS Server: Monitoring: Active Pooled Connections in the Oracle WebLogic Server Administration Console Help.

8.2 Managing JMS Messages

The WebLogic JMS message monitoring and management features allow you to create new messages, delete selected messages, move messages to another queue, export message contents to another file, import message contents from another file, or drain all the messages from the queue.

8.2.1 JMS Message Management Using Java APIs

WebLogic Java Management Extensions JMX enables you to access the JMSDestinationRuntimeMBean and JMSDurableSubscriberRuntimeMBean to manage messages on JMS queues and topic durable subscribers. For more information, see Accessing WebLogic Server MBeans with JMX in Developing Custom Management Utilities With JMX for Oracle WebLogic Server. In WebLogic JMS, there are various states for messages. You can use these states to help manage your messages as described in the following sections. For information on valid message states, see weblogic.jms.extensions.JMSMessageInfo in Oracle WebLogic Server API Reference.

8.2.2 JMS Message Management Using the Administration Console

The JMS Message Management page of the Administration Console summarizes the messages that are available on the standalone queue, distributed queue, or durable topic subscriber you that you are monitoring. You can page through messages andor retrieve a set of messages that meet filtering criteria you specify. You can also customize the message display to show only the information you need. From this