Channel Retry
The Channel Retry configuration category includes the following configurable options:
Failure Channel Name
Retry Delay(ms)
Maximum amount of retry attempts.
Maximum Delay(ms) between attempts.
Retry Channel Name
Retriable Exceptions
Retry Strategy
|
Failure Channel Name |
|
|
STRING | |
The name of Kafka topic or ActiveMQ queue where resources are sent after they have exceeded the maximum number of retry attempts, and have still not been successfully processed. | |
|
|
(no default) | |
|
|
Retry Delay(ms) |
|
|
POSITIVE_INTEGER | |
The minimum amount of time to wait (milliseconds) between retry attempts. | |
|
|
1000
|
|
|
|
Maximum amount of retry attempts. |
|
|
POSITIVE_INTEGER | |
The maximum amount of times to attempt import before considering a message failed. Non-zero value required for retry to be enabled. If set to zero, failed messages will skip the retry channel completely and go directly to the failure channel. | |
|
|
1
|
|
|
|
Maximum Delay(ms) between attempts. |
|
|
POSITIVE_INTEGER | |
The maximum amount of time to wait (milliseconds) between retry attempts. This provides an upper limit for exponential backoff. | |
|
|
1000
|
|
|
|
Retry Channel Name |
|
|
STRING | |
The name of Kafka topic or ActiveMQ queue where inbound resources are sent when a failure occurs during processing of an incoming resource. Non-null value required for retry to be enabled. | |
|
|
(no default) | |
|
|
Retriable Exceptions |
|
|
STRING_MULTILINE | |
A list of Exception classes that indicate processing should be retried. Add one per line. If left blank, all exceptions will be treated as retriable. Any exceptions that are caught that are non-retriable will cause the message to go directly to the failure channel. | |
|
|
(no default) | |
|
|
Retry Strategy |
|
|
ENUM | |
Values |
|
Which backoff strategy to attempt during retries. Valid options are CONSTANT and EXPONENTIAL . Non-null value required for retry to be enabled.
|
|
|
|
CONSTANT
|
|
|