Durable Subscribers

You can search, monitor, and delete durable subscribers for a Universal Messaging server instance. You can browse and purge events on a specific durable subscriber.

Note:

You can purge events only for shared durable subscribers.

Attribute

Description

Name

Name of the durable subscriber.

Channel

Name of the channel to which the durable subscriber belongs.

Durable type

Type of the durable subscriber (Shared, Shared - Queued, Priority, or Durable).

Last event ID

Event ID of the last successfully consumed event.

Outstanding events

The number of events outstanding for a particular durable subscriber.

Note:

The outstanding event count displayed for a non-shared durable is only an estimate.

Last read time

The last date and time when the durable subscriber read, committed, or rolled back an event.

Attribute	Description
Name	Name of the durable subscriber.
Channel	Name of the channel to which the durable subscriber belongs.
Durable type	Type of the durable subscriber (Shared, Shared - Queued, Priority, or Durable).
Cluster-wide	Whether the durable subscriber is on a channel that is part of a Universal Messaging cluster.
Persistent	Whether the durable subscriber is persistent. Persistent durable subscribers retrieve the last event ID consumed before the Universal Messaging server instance was restarted.
Selector	Events are filtered based on the defined selector.

Attribute	Description
Last event ID	Event ID of the last successfully consumed event.
Store size (KB)	The size of the store available for the Shared - Queued durable.
Total events	The number of outstanding events for the durable subscriber.
Pending events	The number of outstanding events waiting for a commit or a rollback.
Last read time	The last date and time when the durable subscriber read, committed, or rolled back an event.
Last write time	The last time the durable was written to. Typically, this is the last time an event was added to the durable subscriber.

Attribute	Description
ID	Connection ID.
Mode	Client subscription mode (subscription based or getNext).
Max pending	Window size specified by the client.
Acknowledged	Total acknowledged events.
Rolled back	Total rolled back events.
Pending	Event queues waiting to be acknowledged or rolled back.
Last read time	Last time the session acknowledged, rolled back, or read an event from the durable subscriber.

The Browse events page displays the event list and lets you to browse events for a durable subscriber. Events are displayed in the order of old to new. A maximum of 1000 events are displayed in the table with a maximum combined size of 10 MB. For example, if two events of size 10 MB and 100 MB are present for the durable subscriber, only the event of size 10 MB is displayed, and no other events are displayed. Click Browse events to refresh the events displayed in the table.

Attribute

Description

Event ID

Unique ID to identify the event.

TTL (ms)

Specifies how long (in milliseconds) each event is retained.

Tag

Shows the tag information of the event if an event tag exists.

Event data

Content of the event.

Note:

If the payload is Protocol Buffers (Protobuf), the event data will contain the message "Protobuf payload" and not the decoded payload.

Event size (bytes)

Size of the event in bytes.

Note:

Event size is the total size of the event that is the sum of event data and event properties.

Event properties

Event properties represented as key-value pairs.

Persistent

Shows whether the event is persistent or not.

The Bulk purge option allows you to purge events in bulk for a durable subscriber. You can purge events by providing an event range, event filter, or purge all the events.