Locking and Unlocking the Forwarding Queue
Before you can modify the contents of a forwarding queue, you must lock the queue. There is no need to lock the queue if you only want to browse the contents. Keep the following points in mind when working with locked forwarding queues:
You can have multiple queues locked at one time.
You must have administrative privileges to lock a queue.
Nonadministrative users on the local
Broker or the remote
Broker cannot clear the contents or delete documents from the forwarding queue in the locked state.
The local
Broker continues to publish to the locked forwarding queue, those documents that have been subscribed to by the remote
Broker.
A remote
Broker cannot retrieve documents from a locked forwarding queue.
While the forwarding queue is locked, remote
Broker processes document acknowledgements even for those documents that it retrieved before you locked the queue.
When you lock a queue,
My webMethods internally creates a volatile client to own the queue lock. This client belongs to the admin client group.
The queue remains locked until you specifically unlock the queue, your
My webMethods session ends, or the volatile client created to hold the queue lock is destroyed.
When you finish working with a queue, unlock the queue so that queue activity, such as document retrieval, can resume. If you log out of My webMethods or if your session expires before you unlock a queue, My webMethods unlocks the queue automatically. Only the user who locked the queue and a My webMethods administrator can unlock a queue.
Follow these steps to lock and unlock the forwarding queue for a remote Broker:
To lock or unlock the forwarding queue for a remote
Broker2. To lock the queue, click the Lock button next to the lock icon. Or, click the Unlock button next to the lock icon to unlock the queue.