Closed sidsamant closed 2 years ago
You are wiring in Boot's auto-configured KafkaTemplate
. Boot knows nothing about binders or binder configuration; it uses the normal Boot spring.kafka....
properties when configuring that template.
Thanks @garyrussell . It worked on configuring the spring.kafka properties as you mentioned.
I assumed it would pick the server settings from the binder configuration based on https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/blob/main/docs/src/main/asciidoc/overview.adoc#retry-and-dead-letter-processing
Reopening; we should improve that documentation.
Issue moved to spring-cloud/spring-cloud-stream #2313 via ZenHub
Little writeup to make it easy for others https://medium.com/@sidsamanta/spring-cloud-stream-kafka-errors-to-dead-letter-queue-dlq-bb4078d9c6a0
Hi,
I am using following dependencies
To forward deserialization errors to DLQ, I added the following bean:
I have the following configuration in application.yml
When the application runs and if there are Deserialization errors, it tries to produce to non-existent
localhost:9092
instead of the brokers in the config. What am I missing?Thanks in advance