oscerd commented on issue #1734:
URL:
https://github.com/apache/camel-kafka-connector/issues/1734#issuecomment-6436869891
## Resolved in 4.22.0
The `NoSuchMethodError: org.apache.kafka.common.utils.Utils.mkSet(...)` came
from a stale transitive `connect-json:3.6.1` pulled in by
`io.apicurio:apicurio-registry-utils-converter:2.5.11.Final`, which breaks on a
Kafka 4.x runtime where `Utils.mkSet` was removed. Thanks @JKrehling for the
precise diagnosis.
This is fixed in **4.22.0** (Kafka 4.2.x) via #1779 / #1778: `connect-json`
is now pinned to `${kafka.version}` in the parent `<dependencyManagement>`, so
every connector resolves it to 4.2.1 no matter what apicurio requests
transitively. Verified on current main:
```
\- io.apicurio:apicurio-registry-utils-converter:jar:2.5.11.Final:compile
\- org.apache.kafka:connect-json:jar:4.2.1:compile
```
**For users:** upgrade to the 4.22.0 connectors (e.g.
`.../camel-<name>-kafka-connector/4.22.0/`). The artifacts under the earlier
version paths still carry the old `connect-json`.
Two follow-ups so this issue stays scoped:
- @aonamrata the error you now hit on 4.22.0 (`camel-aws-s3-source`, failing
in `InternalRouteStartupManager.doWarmUpRoutes`) is a **different problem** —
that connector doesn't use apicurio, and it's a route-startup failure rather
than the `mkSet` plugin-scanning crash. I've opened #1849 for it; the trace you
posted was truncated, so please add the full log (including the root `Caused
by:`) and your connector config there.
- Optional apicurio hygiene — bumping `2.5.11.Final` now that `connect-json`
is pinned — is tracked in #1850.
Closing as fixed in 4.22.0.
---
_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]
