Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# Active JMS Servers

This page displays the active JMS servers defined in your domain. A JMS server manages connections and message requests on behalf of JMS clients. You must first configure a JMS server before you can configure any destinations or session pools.

Monitoring information for a JMS server is available only after you have targeted it to either a WebLogic Server instance or a migratable target on the JMS --> Servers --> Target and Deploy tab.

- For more information on monitoring all active JMS destinations, see Active JMS Destinations.
- For more information on monitoring all active JMS session pools, see Active JMS Session Pools.

Active JMS Server Information

Name — Name of the JMS server.

Connections — Current number of active JMS connections to this WebLogic Server instance. Clicking the number takes you to the Active JMS Connections page, as described in Active JMS Connections.

Active JMS Destinations — Current number of active JMS destinations running on the JMS server. Clicking the number takes you to the Active JMS Destinations page, as described in Active JMS Destinations.

Destinations High — Greatest number of instantiated destinations for the JMS server since the last time the server was booted.

Destinations Total — Total number of instantiated destinations for the JMS server.

Bytes Current — Current number of bytes stored across all destinations for the JMS server. This does not include the pending bytes.

Bytes High — Greatest number of bytes stored across all destinations for the JMS server since the last time the server was booted.

Bytes Pending — The number of bytes that are stored in the system but which are not visible, and therefore cannot be received. 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. Pending bytes are over and above the current number of bytes.

Bytes Received Count — Total number of bytes received across all destinations for the JMS server since the last time the server was booted.

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

Messages — Current number of messages stored across all destinations for the JMS server. This does not include pending messages.

Messages High — Greatest number of messages stored across all destinations for the JMS server 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. 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. Pending messages are over and above the current number of messages.

Messages Received — Total number of messages received for all destinations stored across the JMS server since the last time the server was booted.

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

Session Pools — Current number of session pools defined for the JMS server. Clicking the number takes you to the Active JMS Session Pools page, as described in Active JMS Session Pools.

Session Pools High — Greatest number of session pools instantiated on the JMS server since the last time the server was booted.

Session Pools Total — Total number of instantiated sessions pools on the JMS server since the last time the server was booted.