oscerd opened a new issue, #1849:
URL: https://github.com/apache/camel-kafka-connector/issues/1849
Split out from #1734 (the Kafka 4.x `Utils.mkSet` / stale `connect-json`
crash, now resolved in 4.22.0). The failure below is a **different** problem
and gets its own issue so #1734 can be closed cleanly.
## What was reported
After upgrading to `camel-aws-s3-source-kafka-connector` **4.22.0** on base
image `confluentinc/cp-kafka-connect:8.2.4` (Java 21), the source task fails
while Camel is warming up the route:
```
at
org.apache.camel.impl.engine.InternalRouteStartupManager.doWarmUpRoutes(InternalRouteStartupManager.java:324)
at
org.apache.camel.impl.engine.InternalRouteStartupManager.safelyStartRouteServices(InternalRouteStartupManager.java:193)
at
org.apache.camel.impl.engine.InternalRouteStartupManager.lambda$doStartOrResumeRoutes$0(InternalRouteStartupManager.java:129)
...
at
org.apache.camel.kafkaconnector.CamelSourceTask.start(CamelSourceTask.java:191)
at
org.apache.kafka.connect.runtime.AbstractWorkerSourceTask.initializeAndStart(AbstractWorkerSourceTask.java:288)
...
```
(full trace as posted in #1734)
## Why this is almost certainly not the connect-json issue
- `camel-aws-s3-source` does not use the apicurio converter, so the
`connect-json` pin that fixed #1734 does not touch this code path.
- This is a Camel **route start** failure
(`InternalRouteStartupManager.doWarmUpRoutes`), not a `NoSuchMethodError`
during Connect plugin scanning.
## What we need to diagnose this (@aonamrata)
The stack trace posted is **truncated** — it begins mid-trace (with a stray
control character) and is missing the actual exception type, message and
`Caused by:` chain, which is the part that identifies the root cause. Could you
please provide:
1. The **full, untruncated** task log, from the first `ERROR`/exception line
down through every `Caused by:` — the top of the trace is what we need.
2. The **connector configuration** (JSON or properties), with any secrets
(access keys, tokens) redacted.
3. How the connector was installed (the ZIP from Maven Central under
`.../camel-aws-s3-source-kafka-connector/4.22.0/`, or a local build) and the
exact Camel / Kafka Connect versions in the image.
With the root `Caused by:` we can tell whether this is a missing AWS
configuration property, a classloading/plugin-isolation issue in the
`cp-kafka-connect:8.2.4` image, or a genuine connector bug.
---
_Claude Code on behalf of Andrea Cosentino_
--
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]
