Transient Error Handling Properties
When building a service, you can specify what action Integration Server takes when the service fails because of a transient error caused by a run-time exception. That is, you can specify whether or not Integration Server should retry the service.
In the Properties view, under Transient error handling, you specify whether or not Integration Server should retry the service.
Property | Description |
Max retry attempts | Specifies the number of times Integration Server should attempt to re-execute the service when the service fails because of an ISRuntimeException. An ISRuntimeException occurs when the service catches a transient error, wraps the error, and re-throws it as an exception. (A transient error is an error that arises from a condition that might be resolved quickly, such as the unavailability of a resource due to network issues or failure to connect to a database.) The default is 0, which indicates that Integration Server does not attempt to re-execute the service. |
Retry interval | Specifies the number of milliseconds that Integration Server should wait between retry attempts. The default is 0 milliseconds, which indicates that Integration Server re-executes the service immediately Note: | Integration Server enforces a maximum retry period when you configure service retry properties. The maximum retry period indicates the total amount of time that can elapse if the Integration Server makes the maximum retry attempts. By default, the maximum retry period is 15,000 milliseconds (15 seconds). When you configure service retry, Integration Server verifies that the retry period for that service will not exceed the maximum retry period. Integration Server determines the retry period for the service by multiplying the maximum retry attempts by the retry interval. If this value exceeds the maximum retry period, Designer displays an error indicating that either the maximum attempts or the retry interval needs to be modified. |
|
Contact Support
|
Community
|
Feedback