Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# JMS: Monitoring

[Attributes and Console Screen Reference for JMS]

The following sections explain how to monitor the run-time statistics for your JMS objects from the Administration Console:

- Monitoring Pooled JMS Connections
- Monitoring Active JMS Connections
- Monitoring Active JMS Sessions, Consumers, and Producers
- Monitoring Active JMS Servers
- Monitoring Active JMS Destinations
- Monitoring Durable Subscribers for Topics
- Monitoring Active JMS Session Pools
- Monitoring Distributed Destination System Subscriptions and Proxy Topic Members

You may also want to refer these WebLogic JMS and Messaging Bridge sections:

- JMS: Configuring
- JMS: Tuning
- Messaging Bridge

# Overview

You can monitor statistics for the following JMS objects: JMS servers, connections, pooled connections, destinations, message producers, message consumers, JMS server session pools, and durable subscribers for JMS topics.

JMS statistics continue to increment as long as the server is running. Statistics are reset only when the server is rebooted.

Note: For instructions on monitoring JMS connections to WebLogic Server, refer to Server --> Monitoring --> JMS.

## 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.

1. Expand the Servers node.
2. Select the WebLogic Server instance where you want to monitor JMS connections.
3. Select the Monitoring tab.
4. Select the JMS tab. Totals for JMS server and connection statistics are displayed in the JMS dialog.
5. Click the Monitor all Pooled JMS Connections text link. A table displays showing all the pooled JMS connection for the server, as described in JMS Pooled Connections.

## Monitoring Active JMS Connections

You can monitor statistics on all the active JMS connections on your server. A JMS connection is an open communication channel to the messaging system.

1. Expand the Servers node.
2. Select the WebLogic Server instance where you want to monitor JMS connections.
3. Select the Monitoring tab in the right pane.
4. Select the JMS tab. Totals for JMS server and connection statistics are displayed in the JMS dialog.
5. Click the Monitor all Active JMS Connections text link. A table displays showing all active JMS connection for the server, as described in Active JMS Connections.

## Monitoring Active JMS Sessions, Consumers, and Producers

You can monitor statistics on all the active JMS sessions, consumers, and producers on your server. A session defines a serial order for both the messages produced and the messages consumed, and can create multiple message producers and message consumers. The same thread can be used for producing and consuming messages.

1. Expand the Servers node.
2. Select the WebLogic Server instance where you want to monitor JMS connections.
3. Select the Monitoring tab in the right pane.
4. Select the JMS tab. Totals for JMS server and connection statistics are displayed in the JMS dialog.
5. Click the Monitor all Active JMS Connections text link. A table displays showing all active JMS connection for the server.
6. In the Sessions column, click the hyperlinked number for the session that you want to monitor. The "Active JMS Sessions" table displays with statistics for the consumers and producers that are part of the session, as described in Active JMS Sessions.
7. To drill down for more detailed information about the session's consumers and producers, click the hyperlinked number for the specific consumer or producer that you want to monitor, as described in Active JMS Consumers and Active JMS Producers.

## Monitoring Active JMS Servers

You can monitor statistics on all the active JMS servers defined in your domain. A JMS server manages connections and message requests on behalf of JMS clients.

1. Expand the JMS —> Servers node.
2. The JMS Servers information displays in the right pane showing all the JMS servers defined in your domain.
3. Click the JMS server that you want to monitor from the JMS server list, or from the JMS Servers table displayed in the right pane.
4. Click the Monitoring tab to display the monitoring data.
5. Click the Monitor all Active JMS Servers text link in the right pane.
6. A table displays showing all instances of the JMS server deployed across the WebLogic Server domain, as described in Active JMS Servers.

## Monitoring Active JMS Destinations

You can monitor statistics on all the active destinations currently running on a JMS server. A JMS destinations identify queue (Point-To-Point) or topic (Pub/Sub) destination types for a JMS server

1. Expand the JMS —> Servers node.
2. The JMS Servers table displays in the right pane showing all the JMS servers defined in your domain.
3. Click the JMS server that you want to monitor from the JMS server list, or from the JMS Servers table displayed in the right pane.
4. Click the Monitoring tab to display the monitoring data.
5. Click the Monitor all Active JMS Destinations text link. A table displays in the right pane showing all active JMS destinations for the current domain, as described in Active JMS Destinations.

Note: When monitoring distributed destinations, you may see proxy topic members or system subscriptions for the topic or queue members. For more information see, Monitoring Distributed Destination System Subscriptions and Proxy Topic Members.

## Monitoring Durable Subscribers for Topics

You can monitor statistics on all the durable subscribers that are running on your JMS topics. WebLogic JMS stores durable subscribers in a persistent disk-based file 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.

1. Expand the JMS —> Servers node.
2. The JMS Servers table displays in the right pane showing all the JMS servers defined in your domain.
3. Click the JMS server that you want to monitor from the JMS server list in the left pane, or from the JMS Servers table displayed in the right pane.
4. Click the Monitoring tab to display the monitoring data.
5. Click the Monitor all Active JMS Destinations text link. A table displays in the right pane showing all active JMS destinations for the current domain, with the Durable Subscriber Runtimes column listing the number of durable subscribers running (if any) for the destination topics listed in the table.
6. To view durable subscriber information for a specific topic, click the icon (or actual number) in the Durable Subscriber Runtimes column for the desired topic.
7. Click the Monitor all Durable Subscribers text link. Durable Subscribers information is displayed in a table in the right pane for all durable subscribers running (if any) for the destination topics listed in the table, as described in Durable Subscribers.

## 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.

1. Expand the JMS node —> Servers node.
2. The JMS Servers table displays in the right pane showing all the JMS servers defined in your domain.
3. Click the JMS server that you want to monitor from the JMS server list, or from the JMS Servers table displayed in the right pane.
4. Click the Monitoring tab to display the monitoring data.
5. Click the Monitor all Active JMS Session Pools Runtime text link. A table displays showing all active JMS session pools for the current domain, as described in Active JMS Session Pools.

## Monitoring Distributed Destination System Subscriptions and Proxy Topic Members

In certain distributed destination configurations for Weblogic JMS, the distributed destination may automatically create proxy topic members or system subscriptions between the topic or queue members. If this occurs, system subscriptions and proxy topic members will appear in MBean statistics, as well as in the Administration Console, when monitoring distributed destination members, as described in Active JMS Destinations. They may also appear in the durable subscription names and in the consumer counts for the distributed destination members.

The following points describe the behavior of system subscriptions and proxy topic members:

- Distributed Topic Proxy Members — A WebLogic Server instance that has a configured JMS connection factory, but which has not been configured to host a local distributed topic member for a remote distributed topic, may automatically create and host a local proxy topic member for the remote distributed topic. This occurs when the first non-durable subscription for the distributed topic is created on the server's connection factory. The dynamically-created proxy topic member resides within a dynamically-created JMS server. Each of the manually-configured distributed topic members will create a system subscription for each dynamically-created proxy topic member. The non-durable consumers are then created on the proxy topic member.
- Distributed Topic System Subscriptions — System subscriptions are used to forward messages between configured distributed destination members. For example, when there are n members in a distributed topic, each member has at least n-1 system subscribers. In addition, for each proxy topic member, there will also be a system subscription on each distributed topic member.
- Distributed Queue System Subscriptions — Distributed queue members that have enabled the Forward Delay attribute on the distributed queue (by changing the default value of -1 seconds), may also create system subscribers. The system subscribers are used to forward messages from queue members with no consumers to queue members that do have consumers.
- Durable System Subscriptions — When a JMS file or JDBC store is configured for a distributed topic member, system subscriptions are created as durable subscribers. They are displayed by name in the Administration Console.