Administration Console Online Help

Active JMS Destinations

This table reports the active destinations (queues and topics) currently running on a JMS server. Monitoring information for a JMS server's destinations is available only after you have targeted the JMS server to either a WebLogic Server instance or a migratable target on the JMS --> Servers --> Target and Deploy tab.

To monitor the active durable subscribers for topics running on the JMS server, click the Monitor all Durable Subscribers link.

For more information on monitoring durable subscribers, see Monitoring Durable Subscribers for Topics.
For more information on durable subscribers, see Durable Subscribers.

Active JMS Destination Information

Name — The name of the JMS destination.

Consumers — Current number of registered message consumers accessing the destination.

Note: For a JMS topic that has a message-driven bean (MDB) listening on it, the number of consumers will always equal one. This is because each message to the topic is either processed by a single MDB or by multiple MDB instances in the pool that share the same consumer, which allows multiple messages to be processed in parallel.

Consumers High — Greatest number of registered message consumers accessing the destination since the last time the server was booted.

Consumers Total — Total number of registered message consumers accessing the destination since the last time the server was booted.

Bytes — Current number of bytes stored in the destination. This does not include pending bytes.

Bytes Pending — The number of bytes that are stored in the system but which are not visible, and therefore cannot be received.

For pending queue bytes, byte visibility is affected by various delivery options including, but not limited to, transactions, message delivery and redelivery time, message expiration, and receipt without acknowledgement. The queue bytes pending count is over and above the current number of bytes.
For pending topic bytes, the pending count is a count of all messages that are awaiting consumption by one or more matching subscribers. The topic pending count is incremented by the size of the message when a message is sent, and is decremented by the size of the message when all matching subscribers acknowledge the message or when the message expires. The topic bytes pending count always equals the current number of bytes.

Bytes Received — Number of bytes received by the destination since the last time the server was booted. There is a difference between the number of characters received and number of bytes received. While, in most cases, this value is the same, for multi-byte characters, the number of bytes received exceeds the number of characters.

Note: The Administration Console displays the number of characters received and not the number of bytes received.

Bytes Threshold Time — Amount of time that the destination has spent in a bytes threshold condition since the last time the server was booted.

Messages — Current number of messages stored in the destination. This does not include pending bytes

Messages High — Greatest number of messages stored in the destination since the last time the server was booted.

Messages Pending — The number of messages that are stored in the system but which are not visible, and therefore cannot be received.

For pending queue messages, message visibility is affected by various delivery options including, but not limited to, transactions, message delivery and redelivery time, message expiration, and receipt without acknowledgement. The queue messages pending count is over and above the current number of messages.
For pending topic messages, the pending count is a count of all messages that are awaiting consumption by one or more matching subscribers. The topic pending count is incremented by one when a message sent, and is decremented by one when all matching subscribers acknowledge the message or when the message expires. The topic messages pending count always equals the current number of messages.

Messages Received — Number of messages received by the destination since the last time the server was booted.

Messages Threshold Time — Amount of time that the destination spent in a message threshold condition since the last time the server was booted.