When a webMethods messaging trigger exists on multiple Integration Servers in a cluster or in a non-clustered group, the subscriptions created by the webMethods messaging trigger remain active even if you disable the webMethods messaging trigger from one of the Integration Servers. This is because the client created for the webMethods messaging trigger on the webMethods Broker is shared. The client on the webMethods Broker becomes disconnected when you disable the webMethods messaging trigger on all the servers in the cluster or non-clustered group of servers. Even when the shared webMethods messaging trigger client becomes disconnected, the subscriptions established by the webMethods messaging trigger remain active. The webMethods Broker continues to enqueue documents for the webMethods messaging trigger. When you re-enable the webMethods messaging trigger on any server in the cluster or non-clustered group, all the queued documents that did not expire will be processed.

To disable a webMethods messaging trigger in a cluster or non-clustered group of Integration Servers, disable the webMethods messaging trigger on each Integration Server, and then manually remove the document subscriptions created by the webMethods messaging trigger from the webMethods Broker.