Better exception message header for DLT #2671
Labels
Milestone
Comments
|
Thanks for reporting; in the meantime, you should be able to find the root cause in the stack trace header. |
garyrussell
added a commit
to garyrussell/spring-kafka
that referenced
this issue
May 2, 2023
Resolves spring-projects#2671 With Spring Framework 6, `NestedRuntimeException.getMessage()` no longer includes the messages for nested exceptions via the cause chain. See spring-projects/spring-framework#25162 This means that the DLQ exception message header always contains the same `Failed listener` message. Find the root cause exception of the message and include its message in the header. Ignore any nested `TimestampedException` and `LEFE` between the top `LEFE` and the root cause; these will still appear in the stack trace.
garyrussell
added a commit
to garyrussell/spring-kafka
that referenced
this issue
May 2, 2023
Resolves spring-projects#2671 With Spring Framework 6, `NestedRuntimeException.getMessage()` no longer includes the messages for nested exceptions via the cause chain. See spring-projects/spring-framework#25162 This means that the DLQ exception message header always contains the same `Failed listener` message. Find the root cause exception of the message and include its message in the header. Ignore any nested `TimestampedException` and `LEFE` between the top `LEFE` and the root cause; these will still appear in the stack trace.
garyrussell
added a commit
to garyrussell/spring-kafka
that referenced
this issue
May 2, 2023
Resolves spring-projects#2671 With Spring Framework 6, `NestedRuntimeException.getMessage()` no longer includes the messages for nested exceptions via the cause chain. See spring-projects/spring-framework#25162 This means that the DLQ exception message header always contains the same `Failed listener` message. Find the root cause exception and include its message in the header. Ignore any nested `TimestampedException` and `LEFE` between the top `LEFE` and the root cause; these will still appear in the stack trace.
artembilan
pushed a commit
that referenced
this issue
May 2, 2023
Resolves #2671 With Spring Framework 6, `NestedRuntimeException.getMessage()` no longer includes the messages for nested exceptions via the cause chain. See spring-projects/spring-framework#25162 This means that the DLQ exception message header always contains the same `Failed listener` message. Find the root cause exception and include its message in the header. Ignore any nested `TimestampedException` and `LEFE` between the top `LEFE` and the root cause; these will still appear in the stack trace.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
In DeadLetter messages, the header
KafkaHeaders.DLT_EXCEPTION_MESSAGEshould have message from at least the root cause exception.Current Behavior
The header
KafkaHeaders.DLT_EXCEPTION_MESSAGEis always "Listener failed" which is not really useful.Context
Since spring framework 6.0, we do not have the message from the cause chain anymore.
We can not get any useful information from this header anymore.
The text was updated successfully, but these errors were encountered: