Rewinding a Durable

When retention time is enabled, see, Retention Time an administrator or client application may rewind the durable. Rewinding a durable means that all messages present in the durable, including messages previously acknowledged, are now delivered to newly created subscribers (or browsers). This allows you to replay messages from a durable.

Administrators can rewind any durable through the REST API POST persistence/clusters/<clus_name>/stores/<stor_name>/durables/<dur_name>Or, administrators can rewind a durable through the user interface, see Durables List.

Client applications can rewind any durable via the tibRealm_RewindSubscription() API, or equivalent language binding. If permissions are enabled for persistence, the client must have the subscribe permission to do so. For more information, see :Required Permissions for API Calls

Before rewinding a durable, all subscribers on the durable must be closed. Once rewind completes, subscribers can be created normally, possibly using the exact code as before to process and acknowledge messages.

Rewinding a durable clears the acknowledged status of all messages. However, rewinding a durable does not reset the message's age. For example, rewinding a durable does not cause an acknowledged message to be retained for any longer than normal, and it does not affect the behavior of message TTL.