Topic: Monitoring: Durable Subscribers
Use this page to monitor and manage durable subscribers that are running on a JMS topic. From this page, you can view detailed runtime statistics for each durable subscriber. Click on a subscriber to view its configuration details.
Durable subscribers are persisted to a disk-based file store or a JDBC-accessible database until the message has been delivered to the subscribers or has expired, even if those subscribers are not active when the message is delivered. A durable subscriber registers a durable subscription with a unique identity that is retained by JMS. Subsequent subscriber objects with the same identity resume the subscription in the state it was left by the prior subscriber. If there is no active subscriber for a durable subscription, JMS retains the subscription's messages until they are received by the subscription or until they expire.
Name Description Client ID
A unique client identifier for this durable subscriber.
Note: The client ID is not necessarily equivalent to the WebLogic Server username; that is, a name used to authenticate a user in the WebLogic security realm. You can set the client ID to the WebLogic Server username if it is appropriate for your JMS application.
Client ID Policy
The policy for the client identifier for this durable subscriber.
Note: The client ID policy is either
The subscription name for this durable subscriber. This name must be unique for each client ID.
Valid durable subscription names cannot include the following characters: comma ",", equals "=", colon ":", asterisk "*", percent "%", or question mark"?".
Indicates whether this subscription is being used by a durable subscriber.
Messages Current Count
The number of messages still available by this durable subscriber.
Messages Pending Count
The number of messages pending (uncommitted and unacknowledged) by this durable subscriber.
Bytes Current Count
The number of bytes received by this durable subscriber.
Bytes Pending Count
The number of bytes pending by this durable subscriber.
Last Messages Received Time in Millis
The time when the last time a subscriber received a message from the subscription. The returned value is a standard java absolute time, which is measured in milliseconds since midnight, January 1, 1970 UTC
This returns the JMS durable subscription boot time if there were no messages that were successfully delivered to any subscriber on this subscription since the subscription was booted. We define the boot time of a durable subscription to be the time the subscription is originally created or recovered during a server reboot or jms migration, which ever is latest.
No Local Messages
Specifies whether this durable subscriber receives local messages that it has published.
To prevent this, set the
The message selector defined for this durable subscriber.
Subscribers Current Count
The number of subscribers that currently share this subscription.
Subscribers High Count
The highest number of subscribers that have shared this subscription at the same time since the creation or the last reboot of the subscription, which ever is later.
Subscribers Total Count
The total number of subscribers that have accessed this subscription since the creation or the last reboot of the subscription, whichever is later.
Subscription Sharing Policy
The subscription sharing policy on this subscriber.