Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GH-2662: Kafka binder DLQ root cause message #2812

Merged
merged 1 commit into from
Sep 20, 2023

Conversation

sobychacko
Copy link
Contributor

  • Becasue NestedRuntimeException from Spring Framework core 6.x removed the getMessage method that included the detailMessage with cause in it, the Kafka binder DLQ records no longer include the cause message. Fix this issue by including the cause in the exception message.

See this comment for more details:

Resolves #2662

 - Becasue NestedRuntimeException from Spring Framework core 6.x removed
   the getMessage method that included the detailMessage with cause in it,
   the Kafka binder DLQ records no longer include the cause message.
   Fix this issue by including the cause in the exception message.

See this comment for more details:
 - spring-cloud#2662 (comment)
This fix is based on the following Spring Kafka commit.
 - spring-projects/spring-kafka@6f58505

Resolves spring-cloud#2662
Copy link
Contributor

@garyrussell garyrussell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but the PR build failed for an unrelated reason.

@sobychacko
Copy link
Contributor Author

@garyrussell What was the failure?

@garyrussell
Copy link
Contributor

A bunch of test failures; click on details. in the "All checks have failed".

@sobychacko
Copy link
Contributor Author

Ah, I think you can ignore those for the time being. Jenkins main CI is all good. This is a new ci-pr we added last week that needs to be cleaned up with a few things.

@garyrussell garyrussell merged commit e06d4ee into spring-cloud:main Sep 20, 2023
1 check failed
@sobychacko sobychacko added the bug label Sep 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Kafka message no longer processed after upgrading from Spring Cloud Stream 3.2.4 to 4.0.1
2 participants