Fatal Error Handling for a webMethods Messaging Trigger
If a webMethods messaging trigger processes documents serially, you can configure fatal error handling for the webMethods messaging trigger. A fatal error occurs when the trigger service ends because of an exception. You can specify that Integration Server suspend the webMethods messaging trigger automatically if a fatal error occurs during trigger service execution. Specifically, Integration Server suspends document retrieval and document processing for the webMethods messaging trigger if the associated trigger service ends because of an exception.
When Integration Server suspends document processing and document retrieval for a webMethods messaging trigger, Integration Server writes the following message to the journal log:
Serial trigger triggerName has been automatically suspended due
to an exception.
Document processing and document retrieval remain suspended until one of the following occurs:
You specifically resume document retrieval or document processing for the
webMethods messaging trigger. You can resume document retrieval and document processing using
Integration Server Administrator, built-in services (
pub.trigger:resumeProcessing or
pub.trigger:resumeRetrieval), or by calling methods in the Java API (com.wm.app.b2b.server.dispatcher.trigger.TriggerFacade.setProcessingSuspended() and com.wm.app.b2b.server.dispatcher.trigger.TriggerFacade.setRetrievalSuspended()).
Integration Server restarts, the
webMethods messaging trigger is enabled or disabled (and then re-enabled), the package containing the
webMethods messaging trigger reloads. (When
Integration Server suspends document retrieval and document processing for a
webMethods messaging trigger because of an error,
Integration Server considers the change to be temporary. For more information about temporary vs. permanent state changes for
webMethods messaging triggers, see
webMethods Integration Server Administrator’s Guide.)
For more information about resuming document processing and document retrieval, see webMethods Integration Server Administrator’s Guide and the webMethods Integration Server Built-In Services Reference.
Automatic suspension of document retrieval and processing can be especially useful for serial webMethods messaging triggers that are designed to process a group of documents in a particular order. If the trigger service ends in error while processing the first document, you might not want to the webMethods messaging trigger to proceed with processing the subsequent documents in the group. If Integration Server automatically suspends document processing, you have an opportunity to determine why the trigger service did not execute successfully and then resubmit the document using webMethods Monitor.
By automatically suspending document retrieval as well, Integration Server prevents the webMethods messaging trigger from retrieving more documents. Because Integration Server already suspended document processing, new documents would just sit in the trigger queue. If Integration Server does not retrieve more documents for the webMethods messaging trigger and Integration Server is in a cluster, the documents might be processed more quickly by another Integration Server in the cluster.
