pub.trigger:suspendJMSTriggers
WmPublic. Suspends one or more JMS triggers.
Input Parameters
triggerNameList | String List Specifies the JMS triggers that you want to suspend. |
applyChangeAcross Cluster | String Optional. Flag indicating whether the specified JMS triggers should be suspended across all the servers in the cluster. Set to:  true to suspend the specified JMS triggers on all the nodes in the cluster. Note:
To make the status change on all the servers in a cluster, the 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 suspend the JMS triggers on the local Integration Server only. This is the default. |
Output Parameters
None.
Usage Notes
When a JMS trigger is suspended, the JMS trigger is running and connected to the JMS provider. Integration Server has stopped message retrieval, but continues processing any messages it has already retrieved. Integration Server enables the JMS trigger automatically upon server restart or when the package containing the JMS trigger reloads.
If you suspend 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.
If a JMS trigger is processing messages when this service executes, the JMS trigger will complete processing. JMS trigger also acknowledges the messages to the JMS provider.
After a suspending a JMS trigger, Integration Server will not start processing for any additional messages already received by the JMS trigger.
Use the
pub.trigger:disableJMSTriggers service to disable one or more JMS triggers.
Use the
pub.trigger:enableJMSTriggers service to enable one or more JMS triggers.
You can also use the Messaging > JMS triggers pages 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