Repository navigation
Build: Align netty-tcnative with netty-handler 4.2.x - #18397
Open
developer-rpai wants to merge 1 commit into
Open
developer-rpai wants to merge 1 commit into
developer-rpai wants to merge 1 commit into
Conversation
…t runtime The root build forces all io.netty 4.2.x artifacts to 4.2.18.Final, but netty-tcnative (2.0.x versioning) was left at the azure-sdk-bom managed 2.0.78.Final. netty-handler 4.2.18 calls SSL.getGroupName(long), added in tcnative 2.0.81, so Azure Blob Storage writes from the Kafka Connect runtime fail with NoSuchMethodError on the first TLS handshake. Pin netty-tcnative to 2.0.84.Final in the version catalog and align all io.netty tcnative 2.0.x artifacts in the global dependency resolution rule, mirroring the existing netty 4.1/4.2 CVE alignment. Fixes apache#18395 Generated-by: Muse Spark (Meta)
This branch has not been deployed
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
1 participant
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.
Kafka Connect runtime 1.12.0 fails Azure Blob Storage writes with NoSuchMethodError on SSL.getGroupName(long) during the first TLS handshake. The root build pins all io.netty 4.2.x artifacts to 4.2.18.Final, but netty-tcnative uses 2.0.x versioning so it was left at the azure-sdk-bom managed 2.0.78.Final, while netty-handler 4.2.18 requires tcnative >= 2.0.81. This pins netty-tcnative to 2.0.84.Final in the version catalog and extends the global dependency alignment rule to io.netty tcnative 2.0.x artifacts, mirroring the existing netty CVE alignment.
Fixes #18395
Test plan: new TestNettyTcnativeCompatibility in the kafka-connect-runtime module asserts SSL.getGroupName(long) is present on the resolved tcnative classes without initializing native code. Verified locally against real jars: passes with 2.0.84.Final, fails with 2.0.78.Final. The full Gradle build could not run in this sandbox, so CI is the real confirmation.
AI Disclosure