Repository navigation
Refs #1849: document the AWS SDK HTTP client conflict on Confluent Platform images - #1851
Merged
Merged
Conversation
…ent Platform images AWS connectors 4.22.0 fail on cp-kafka-connect images with "ServiceConfigurationError: ... ApacheSdkHttpService not a subtype": the image's own AWS SDK (kafka-serde-tools) registers the classic apache-client on the worker classpath, which the plugin can see. Add a Known Incompatibilities entry with the cause and three workarounds. The Camel fix is CAMEL-26343. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Andrea Cosentino <ancosen@gmail.com>
Croway
approved these changes
Oct 27, 2026
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
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.
Refs #1849. The issue stays open until CKC moves to a Camel release with the fix (CAMEL-26343).
Problem
On Confluent Platform
cp-kafka-connectimages, the 4.22.0 AWS connectors fail when the task starts:The image puts its own AWS SDK on the worker classpath (
/usr/share/java/kafka-serde-tools, with the classicapache-client). The plugin class loader also returns the worker'sMETA-INF/servicesregistration. Since Camel 4.22.0 (CAMEL-23866) the connectors ship onlyapache5-client, soApacheSdkHttpServiceloads from the worker and the AWS SDK lookup fails. 4.18.x shippedapache-clientitself, which hid the problem.Change
This adds an "AWS connectors on Confluent Platform images" entry under Known Incompatibilities in
contributor-guide/troubleshooting.adoc. It gives the symptom, the cause and three workarounds:apache-client2.50.2 and its dependencies to the connector directory. Verified incp-kafka-connect:8.2.4with the reporter's configuration, as far as the first S3 call.software.amazon.awssdk.http.service.implinKAFKA_OPTS. This applies to the whole worker JVM.apache-clientjar, when nothing else on the worker uses that AWS SDK.The fix belongs in Camel. CAMEL-26343 (apache/camel#28563) makes the AWS components set their HTTP client themselves. CKC gets it with the Camel 4.22.x release that contains it.
This is a docs-only change, so there is no build or test run. The commit title uses
Refs #1849rather thanFix #1849so that merging this does not close the issue.Claude Code on behalf of Andrea Cosentino
🤖 Generated with Claude Code