Unblocking the Forwarding Queue in a Territory Gateway or Cluster Gateway

If you observe that an internal event in the forwarding queue for a remote Broker is blocking the queue and not allowing events to flow across, you must delete and recreate the remote Broker. If the Broker belongs to a territory gateway or cluster gateway, delete and recreate the blocked-half of the gateway.

To unblock the forwarding queue in a territory gateway or cluster gateway

Note:
While changing a territory gateway configuration or cluster gateway configuration, allow some time for metadata changes to completely propagate across the network.

1. Create a backup of all the regular events contained in all the forwarding queues by saving the events to an external file. For more information about viewing events, see Viewing Queue Content and Administering webMethods Broker.

2. Save the gateway configuration. For more information about importing and exporting Broker metadata, see Administering webMethods Broker.

3. Delete the blocked-half of the gateway. For more information, see Creating and Destroying Gateways, and Creating and Destroying Cluster Gateways.

4. Reconfigure the gateway. For more information about importing and exporting Broker metadata, see Administering webMethods Broker.

5. Restore all the regular events to their respective forwarding queues. For more information, see Inserting Documents.

Note:
Because a Broker in a territory or cluster can have multiple forwarding queues, the backup of the forwarding queue events must be restored (reinserted) in the correct forwarding queue.