webMethods 10.2 | Service Development Help | Working with JMS Triggers | Transient Error Handling for Non-Transacted JMS Triggers | Handling Retry Failure
 
Handling Retry Failure
 
Overview of Throw Exception for Retry Failure
Overview of Suspend and Retry Later for Retry Failure
Retry failure occurs for a standard JMS trigger when Integration Server makes the maximum number of retry attempts and the trigger service still fails because of an ISRuntimeException. Retry failure occurs for a SOAP-JMS trigger when Integration Server makes the maximum number of retry attempts to process a web service operation and the operation still fails because of an ISRuntimeException.
When you configure retry properties, you can specify one of the following actions to determine how Integration Server handles retry failure for a trigger.
*Throw exception. When Integration Server exhausts the maximum number of retry attempts, Integration Server treats the last trigger service or web service operation failure as a service error. This is the default behavior.
*Suspend and retry later. When Integration Server reaches the maximum number of retry attempts, Integration Server suspends the trigger and then retries the trigger service or web service operation at a later time.
Overview of Throw Exception for Retry Failure
Overview of Suspend and Retry Later for Retry Failure

Copyright © 2017-2018 | 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