THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Dead Letter Channel
Camel supports the Dead Letter Channel from the EIP patterns using the DeadLetterChannel processor which is an Error Handler.
Redelivery
It is common for a temporary outage or database deadlock to cause a message to fail to process; but the chances are if its tried a few more times with some time delay then it will complete fine. So we typically wish to use some kind of redelivery policy to decide how many times to try redeliver a message and how long to wait before redelivery attempts.
...
Once all attempts at redelivering the message fails then the message is forwarded to the dead letter queue.
Redelivery default values
The default redeliver policy will use the following values:
...
Camel will log delivery failures at the ERROR logging level by default. You can change this by specifying retriesExhaustedLogLevel and/or retryAttemptedLogLevel. See ExceptionBuilderWithRetryLoggingLevelSetTest for an example.
Redelivery header
When a message is redelivered the DeadLetterChannel will append a customizable header to the message to indicate how many times its been redelivered. The default value is org.apache.camel.redeliveryCount.
The header org.apache.camel.Redelivered contains a boolean if the message is redelivered or not.
Configuring via the DSL
The following example shows how to configure the Dead Letter Channel configuration using the DSL
...
| Include Page | ||||
|---|---|---|---|---|
|