oscerd opened a new pull request, #1851: URL: https://github.com/apache/camel-kafka-connector/pull/1851
Refs #1849. The issue stays open until CKC moves to a Camel release with the fix (CAMEL-26343). ### Problem On Confluent Platform `cp-kafka-connect` images, the 4.22.0 AWS connectors fail when the task starts: ``` java.util.ServiceConfigurationError: software.amazon.awssdk.http.SdkHttpService: software.amazon.awssdk.http.apache.ApacheSdkHttpService not a subtype ``` The image puts its own AWS SDK on the worker classpath (`/usr/share/java/kafka-serde-tools`, with the classic `apache-client`). The plugin class loader also returns the worker's `META-INF/services` registration. Since Camel 4.22.0 (CAMEL-23866) the connectors ship only `apache5-client`, so `ApacheSdkHttpService` loads from the worker and the AWS SDK lookup fails. 4.18.x shipped `apache-client` itself, 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: - Add `apache-client` 2.50.2 and its dependencies to the connector directory. Verified in `cp-kafka-connect:8.2.4` with the reporter's configuration, as far as the first S3 call. - Set `software.amazon.awssdk.http.service.impl` in `KAFKA_OPTS`. This applies to the whole worker JVM. - Remove the image's `apache-client` jar, 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 #1849` rather than `Fix #1849` so that merging this does not close the issue. _Claude Code on behalf of Andrea Cosentino_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
