DevOps Edition for Continuous Integration 10.4 | Service Development Help | Working with JMS Triggers | Transient Error Handling for Non-Transacted JMS Triggers | Handling Retry Failure | Overview of Throw Exception for Retry Failure
 
Overview of Throw Exception for Retry Failure
The following table provides an overview of how Integration Server handles retry failure when the Throw exception option is selected.
Step
Description
1
Integration Server makes the final retry attempt and the trigger service or web service operation fails because of an ISRuntimeException.
2
Integration Server treats the last trigger service or web service operation failure as a ServiceException.
3
Integration Server rejects the message.
If the message is persistent, Integration Server returns an acknowledgement to the JMS provider.
4
Integration Server generates a JMS retrieval failure event if the watt.server.jms.trigger.raiseEventOnRetryFailure property is set to true (the default).
5
If the JMS trigger is configured to suspend on error when a fatal error occurs, Integration Server suspends the JMS trigger. Otherwise, Integration Server processes the next message for the JMS trigger.
In summary, the default retry failure behavior (Throw exception) rejects the message and allows the trigger to continue with message processing when retry failure occurs for a trigger service.
Copyright © 2017-2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release