About Transient Error Handling for a webMethods Messaging Trigger
When building a webMethods messaging trigger, you can specify whether or not Integration Server retries a trigger service when the trigger service fails because of a transient error caused by a run-time exception.
A run-time exception (specifically, an ISRuntimeException) occurs when the trigger service catches and wraps a transient error and then reissues it as an ISRuntimeException. A transient error is an error that arises from a temporary condition that might be resolved or corrected quickly, such as the unavailability of a resource due to network issues or failure to connect to a database. Because the condition that caused the trigger service to fail is temporary, the trigger service might execute successfully if the Integration Server waits and then re-executes the service.
You can configure transient error handling for a webMethods messaging trigger to instruct Integration Server to wait an specified time interval and then re-execute a trigger service automatically when an ISRuntimeException occurs. Integration Server re-executes the trigger service using the original input document.
When you configure transient error handling for a webMethods messaging trigger, you specify the following retry behavior:
Whether
Integration Server should retry trigger services for the
webMethods messaging trigger. Keep in mind that a trigger service can retry only if it is coded to throw ISRuntimeExceptions.
The maximum number of retry attempts
Integration Server should make for each trigger service.
The time interval between retry attempts.
How to handle a retry failure. That is, you can specify what action
Integration Server takes if all the retry attempts are made and the trigger service still fails because of an ISRuntimeException.
You can also configure Integration Server and/or a webMethods messaging trigger to handle transient errors that occur during trigger preprocessing. The trigger preprocessing phase encompasses the time from when a trigger first receives a message from it’s local queue on webMethods messaging trigger to the time the trigger service executes.