Package org.apache.camel.spring.xml

Class ErrorHandlerDefinition

  • @Metadata(label="spring,configuration,error")
public class ErrorHandlerDefinition
extends org.apache.camel.model.IdentifiedType
    Error handler settings

    • Method Detail

      • setDeadLetterUri

        public void setDeadLetterUri​(String deadLetterUri)
        The dead letter endpoint uri for the Dead Letter error handler.

      • setDeadLetterHandleNewException

        public void setDeadLetterHandleNewException​(String deadLetterHandleNewException)
        Whether the dead letter channel should handle (and ignore) any new exception that may been thrown during sending the message to the dead letter endpoint.

        The default value is true which means any such kind of exception is handled and ignored. Set this to false to let the exception be propagated back on the Exchange. This can be used in situations where you use transactions, and want to use Camel's dead letter channel to deal with exceptions during routing, but if the dead letter channel itself fails because of a new exception being thrown, then by setting this to false the new exceptions is propagated back and set on the Exchange, which allows the transaction to detect the exception, and rollback.

      • getLevel

        public org.apache.camel.LoggingLevel getLevel()

      • setLevel

        public void setLevel​(org.apache.camel.LoggingLevel level)
        Logging level to use when using the logging error handler type.

      • setRollbackLoggingLevel

        public void setRollbackLoggingLevel​(org.apache.camel.LoggingLevel rollbackLoggingLevel)
        Sets the logging level to use for logging transactional rollback.

        This option is default WARN.

      • setLogName

        public void setLogName​(String logName)
        Name of the logger to use for the logging error handler

      • setUseOriginalMessage

        public void setUseOriginalMessage​(Boolean useOriginalMessage)
        Will use the original input Message (original body and headers) when an Exchange is moved to the dead letter queue.

        Notice: this only applies when all redeliveries attempt have failed and the Exchange is doomed for failure.
        Instead of using the current inprogress Exchange IN message we use the original IN message instead. This allows you to store the original input in the dead letter queue instead of the inprogress snapshot of the IN message. For instance if you route transform the IN body during routing and then failed. With the original exchange store in the dead letter queue it might be easier to manually re submit the Exchange again as the IN message is the same as when Camel received it. So you should be able to send the Exchange to the same input.

        The difference between useOriginalMessage and useOriginalBody is that the former includes both the original body and headers, where as the latter only includes the original body. You can use the latter to enrich the message with custom headers and include the original message body. The former wont let you do this, as its using the original message body and headers as they are. You cannot enable both useOriginalMessage and useOriginalBody.

        Important: The original input means the input message that are bounded by the current UnitOfWork. An unit of work typically spans one route, or multiple routes if they are connected using internal endpoints such as direct or seda. When messages is passed via external endpoints such as JMS or HTTP then the consumer will create a new unit of work, with the message it received as input as the original input. Also some EIP patterns such as splitter, multicast, will create a new unit of work boundary for the messages in their sub-route (eg the splitted message); however these EIPs have an option named shareUnitOfWork which allows to combine with the parent unit of work in regard to error handling and therefore use the parent original message.

        By default this feature is off.

        See Also:
        setUseOriginalBody(Boolean)

      • setUseOriginalBody

        public void setUseOriginalBody​(Boolean useOriginalBody)
        Will use the original input Message body (original body only) when an Exchange is moved to the dead letter queue.

        Notice: this only applies when all redeliveries attempt have failed and the Exchange is doomed for failure.
        Instead of using the current inprogress Exchange IN message we use the original IN message instead. This allows you to store the original input in the dead letter queue instead of the inprogress snapshot of the IN message. For instance if you route transform the IN body during routing and then failed. With the original exchange store in the dead letter queue it might be easier to manually re submit the Exchange again as the IN message is the same as when Camel received it. So you should be able to send the Exchange to the same input.

        The difference between useOriginalMessage and useOriginalBody is that the former includes both the original body and headers, where as the latter only includes the original body. You can use the latter to enrich the message with custom headers and include the original message body. The former wont let you do this, as its using the original message body and headers as they are. You cannot enable both useOriginalMessage and useOriginalBody.

        Important: The original input means the input message that are bounded by the current UnitOfWork. An unit of work typically spans one route, or multiple routes if they are connected using internal endpoints such as direct or seda. When messages is passed via external endpoints such as JMS or HTTP then the consumer will create a new unit of work, with the message it received as input as the original input. Also some EIP patterns such as splitter, multicast, will create a new unit of work boundary for the messages in their sub-route (eg the splitted message); however these EIPs have an option named shareUnitOfWork which allows to combine with the parent unit of work in regard to error handling and therefore use the parent original message.

        By default this feature is off.

        See Also:
        setUseOriginalMessage(Boolean)

      • setOnRedeliveryRef

        public void setOnRedeliveryRef​(String onRedeliveryRef)
        Sets a reference to a processor that should be processed before a redelivery attempt.

        Can be used to change the Exchange before its being redelivered.

      • setOnExceptionOccurredRef

        public void setOnExceptionOccurredRef​(String onExceptionOccurredRef)
        Sets a reference to a processor that should be processed just after an exception occurred. Can be used to perform custom logging about the occurred exception at the exact time it happened.

        Important: Any exception thrown from this processor will be ignored.

      • setOnPrepareFailureRef

        public void setOnPrepareFailureRef​(String onPrepareFailureRef)
        Sets a reference to a processor to prepare the Exchange before handled by the failure processor / dead letter channel. This allows for example to enrich the message before sending to a dead letter queue.

      • setRetryWhileRef

        public void setRetryWhileRef​(String retryWhileRef)
        Sets a reference to an retry while expression.

        Will continue retrying until expression evaluates to false.

      • setRedeliveryPolicyRef

        public void setRedeliveryPolicyRef​(String redeliveryPolicyRef)
        Sets a reference to a RedeliveryPolicy to be used for redelivery settings.

      • setExecutorServiceRef

        public void setExecutorServiceRef​(String executorServiceRef)
        Sets a reference to a thread pool to be used by the error handler