Page History

...

Changes:

• Adding the errors.deadletterqueuedead.letter.queue.topic.name configuration. This configuration is only modifying the behavior of the out of the box exceptions handlers and would have no effect if a custom exception handlers is implemented, for example:
  • if errors.deadletterqueuedead.letter.queue.topic.name=null (default), then no records are sent to any dead letter queue
  • if errors.dead.letter.deadletterqueuequeue.topic.name is set, exceptions happening during processing, production or deserialization will result in the raw source messages that trigger the topology to be send to the DLQ topic. The processing might or might not continue depending of the configuration of the processing.exception.handler, default.production.exception.handler and default.deserialization.exception.handler configurations

public static final String ERRORS_DEAD_LETTER_DEADLETTERQUEUEQUEUE_TOPIC_NAME_CONFIG = "errors.dead.deadletterqueueletter.queue.topic.name";

.define(ERRORS_DEADLETTERQUEUEDEAD_LETTER_QUEUE_TOPIC_NAME_CONFIG,
       Type.STRING,
       null, /* default */
       Importance.MEDIUM,
       ERRORS_DEAD_DEADLETTERQUEUELETTER_QUEUE_TOPIC_NAME_DOC)

If the user implements a custom exception handler, it is up to the custom handler to build DLQ records to send, in this case, the errors.deadletterqueue.topic.name configuration has no impact.

...