pub.trigger:disableJMSTriggers
WmPublic. Disables one or more JMS triggers.
Input Parameters
triggerNameList | String List Specifies the JMS triggers that you want to disable. |
applyChangeAcross Cluster | String Optional. Flag indicating whether the specified JMS triggers should be disabled across all the servers in the cluster. Set to:  true to disable the specified JMS triggers on all the nodes in the cluster. Note:
To make the state change on all the servers in a cluster, Integration Server must be configured to synchronize trigger changes across the cluster. For more information about configuring an Integration Server to synchronize trigger management changes across a cluster, see webMethods Integration Server Administrator’s Guide. false to disable the JMS triggers on the local Integration Server only. This is the default. |
Output Parameters
None.
Usage Notes
When a JMS trigger is disabled, the JMS trigger is stopped. Integration Server neither retrieves nor processes messages for the JMS trigger. The JMS trigger remains in this state until you enable the trigger.
When you disable a JMS trigger that has a non-durable subscriber, the JMS provider will remove any messages for the JMS trigger.
If you disable a SOAP-JMS trigger that acts as a listener for one or more provider web service descriptors, Integration Server will not retrieve any messages for those web service descriptors.
When you disable a JMS trigger, Integration Server does the following:
If the JMS trigger is waiting before making a retry attempt,
Integration Server interrupts processing for the JMS trigger.
If the JMS trigger is currently processing messages,
Integration Server waits a specified amount of time before forcing the JMS trigger to stop processing messages. If it does not complete in the allotted time the message consumer used to receive messages for the JMS trigger is stopped and the JMS session is closed. At this point the server thread for the JMS trigger continues to run to completion. However, the JMS trigger will not be able to acknowledge the message when processing completes. If the message is guaranteed (PERSISTENT), this can lead to duplicate messages.
The time Integration Server waits between the request to disable the JMS trigger and forcing the trigger to stop is specified by the watt.server.jms.trigger.stopRequestTimeout property
Because administered objects, like destinations, are configured outside of Integration Server, disabling a JMS trigger has no impact on the subscription.
Use the
pub.trigger:enableJMSTriggers service to enable one or more JMS triggers.
Use the
pub.trigger:suspendJMSTriggers service to suspend one or more JMS triggers.
You can also use the Messaging > JMS triggers page in Integration Server Administrator to disable, enable, and suspend JMS triggers. For more information, see webMethods Integration Server Administrator’s Guide.
If you set applyChangeAcrossCluster to true and the synchronization is not successful, the following occurs:
If
Integration Server does not update all the
Integration Servers in the cluster successfully, the
Integration Server writes the following server log entry for each server that could not be updated:
[ISS.0098.0107E] Error occurred during cluster invoke:
Alias = remoteAliasName; Service = serviceName; Exception = exceptionName
The Integration Server Administrator also displays the following message:
[ISS.0085.9203] Errors occurred while updating remote aliases
(x of y updates failed). See server logs for more details.
If
Integration Server cannot update the
Integration Servers in the cluster because the change could not be made locally, the
Integration Server Administrator displays the following message:
[ISS.0085.9204] Local update failed: Exception providing reason for failure.
(Note: The cluster synchronization will not run until all local errors are
resolved.)
If
Integration Server cannot update the other
Integration Servers in the cluster because cluster synchronization is not configured, the
Integration Server writes the following server log entry:
[ISS.0033.0156W] Cluster invoke did not complete successfully.
Cluster Synchronization feature is not configured.
See Also