Transient Error Handling for an MQTT Trigger
For an MQTT trigger, you can specify what action Integration Server takes 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 Integration Server waits and then re-executes the service.
You can configure transient error handling for an MQTT trigger to instruct Integration Server to wait a 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.
When you configure transient error handling for an MQTT trigger, you specify the following retry behavior:
Whether
Integration Server should retry trigger services for the MQTT 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.