Move core error handling docs to top-level
Kafka binder error channels docs cleanup
This commit is contained in:
@@ -18,13 +18,13 @@
|
||||
*** xref:spring-cloud-stream/producing-and-consuming-messages.adoc[]
|
||||
*** xref:spring-cloud-stream/event-routing.adoc[]
|
||||
*** xref:spring-cloud-stream/post-processing-after-sending-message.adoc[]
|
||||
*** xref:spring-cloud-stream/overview-error-handling.adoc[]
|
||||
** xref:spring-cloud-stream/binders.adoc[]
|
||||
*** xref:spring-cloud-stream/overview-binder-api.adoc[A pluggable Binder SPI]
|
||||
*** xref:spring-cloud-stream/binder-detection.adoc[]
|
||||
*** xref:spring-cloud-stream/multiple-binders.adoc[]
|
||||
*** xref:spring-cloud-stream/multiple-systems.adoc[]
|
||||
*** xref:spring-cloud-stream/binder-customizer.adoc[]
|
||||
** xref:spring-cloud-stream/overview-error-handling.adoc[]
|
||||
** xref:observability.adoc[]
|
||||
** xref:spring-cloud-stream/configuration-options.adoc[]
|
||||
*** xref:spring-cloud-stream/binding-service-properties.adoc[]
|
||||
|
||||
@@ -2,12 +2,12 @@
|
||||
= Error Channels
|
||||
|
||||
Starting with version 1.3, the binder unconditionally sends exceptions to an error channel for each consumer destination and can also be configured to send async producer send failures to an error channel.
|
||||
See https://cloud.spring.io/spring-cloud-static/spring-cloud-stream/current/reference/html/spring-cloud-stream.html#spring-cloud-stream-overview-error-handling[this section on error handling] for more information.
|
||||
See xref:spring-cloud-stream/overview-error-handling.adoc[this section on error handling] for more information.
|
||||
|
||||
The payload of the `ErrorMessage` for a send failure is a `KafkaSendFailureException` with properties:
|
||||
|
||||
* `failedMessage`: The Spring Messaging `Message<?>` that failed to be sent.
|
||||
* `record`: The raw `ProducerRecord` that was created from the `failedMessage`
|
||||
|
||||
There is no automatic handling of producer exceptions (such as sending to a <<kafka-dlq-processing, Dead-Letter queue>>).
|
||||
There is no automatic handling of producer exceptions (such as sending to a xref:kafka/kafka-binder/dlq.adoc[dead letter topic]).
|
||||
You can consume these exceptions with your own Spring Integration flow.
|
||||
|
||||
Reference in New Issue
Block a user