SpringCloud/spring-cloud-stream
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarify that having a custom error handler disables auto send to DLQ

Browse Source
This commit is contained in:
Destan Sarpkaya
2025-01-03 16:40:39 +03:00
committed by GitHub
parent 3f8b7003e7
commit 9b1fbfb59d
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/modules/ROOT/pages/spring-cloud-stream/overview-error-handling.adoc
View File

@@ -48,7 +48,8 @@ While acceptable in some cases, for most cases, it is not, and we need some reco
In the previous section we mentioned that by default messages that resulted in error are effectively logged and dropped. The framework also exposes mechanism for you
to provide custom error handler (i.e., to send notification or write to database, etc). You can do so by adding `Consumer` that is specifically designed to accept `ErrorMessage` which aside from all the information about the error (e.g., stack trace etc) contains the original message (the one that triggered the error).
NOTE: Custom error handler is mutually exclusive with framework provided error handlers (i.e., logging and binder error handler - see previous section) to ensure that they do not interfere.
NOTE: Custom error handler is mutually exclusive with framework provided error handlers (i.e., logging error handler and binder specific error handler - see previous section) to ensure that they do not interfere. When you provide a custom error handler, sending failed messages to DLQ won't work even if it is configured to do so.
[source,java]
----