Expired documents in the forwarding queues; that is, documents that have completed their "time to live" period, are deleted only when a remote Broker tries to retrieve them. In cases where a remote Broker does not retrieve documents frequently, this can lead to overloaded queues or memory overflow, which can further affect operations of other Brokers in the topology.

To significantly minimize the memory usage, you can proactively delete the expired volatile documents from the forwarding queues even before the remote Broker tries to retrieve them. Expired documents are deleted whenever the total memory used by the volatile documents exceeds the specified threshold limit.

You can proactively delete volatile documents from a queue by setting the queue-cleanup-enable and the queue-cleanup-threshold parameters in the awbroker.cfg file of each Broker Server instance.

You proactively delete documents from the forwarding queue in the same manner as you would delete them from a client queue. For more information, see Proactively Deleting Documents from a Client Queue.