KAFKA-20168: Downgrade Jetty from 12.0.32 to 12.0.25 to fix SLF4J 2.x incompatibility (4.2)#21560
Closed
mingyen066 wants to merge 1 commit intoapache:4.2from
Closed
KAFKA-20168: Downgrade Jetty from 12.0.32 to 12.0.25 to fix SLF4J 2.x incompatibility (4.2)#21560mingyen066 wants to merge 1 commit intoapache:4.2from
mingyen066 wants to merge 1 commit intoapache:4.2from
Conversation
Jetty 12.0.30+ introduced SLF4J 2.x fluent API usage (Logger.atDebug()) which causes NoSuchMethodError at runtime since Kafka still uses SLF4J 1.7.x. Downgrade to 12.0.25 which includes the CVE-2025-5115 fix without the SLF4J 2.x dependency.
mingyen066
changed the title
Member
|
cherry-pick a8c726a |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Jetty 12.0.30+ introduced SLF4J 2.x fluent API usage (
Logger.atDebug()) which causesNoSuchMethodErrorat runtime since Kafka still uses SLF4J 1.7.x. Downgrade to 12.0.25 which includes the CVE-2025-5115 fix without the SLF4J 2.x incompatibility.The issue was discovered and discussed in #21452 (comment).
trunk: #21559