Java17环境下Kafka3.2/Confluent7.2无法加载Ignite类问题求助

问题背景 #

Java 11环境下运行正常的Kafka 3.2/Confluent Platform 7.2分布式Kafka Connect服务（已安装Ignite kafka-ext模块），切换至Java 17后抛出NoClassDefFoundError，提示无法初始化org.apache.ignite.internal.util.IgniteUtils类。相关Jar包已添加至Kafka Connect的类路径，但问题仍存在。

相关信息 #

启动命令 #

cp-kafk+ 1195088  255  5.6 6174016 915684 ?      Ssl  09:54   0:40 /etc/alternatives/jre_17/bin/java -Xms256M -Xmx2G -server -XX:+UseG1GC -XX:MaxGCPauseMillis=20 -XX:InitiatingHeapOccupancyPercent=35 -XX:+ExplicitGCInvokesConcurrent -XX:MaxInlineLevel=15 -Djava.awt.headless=true -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dkafka.logs.dir=/var/log/kafka -Dlog4j.configuration=file:/etc/kafka/connect-log4j.properties -cp /usr/share/java/kafka/*:/usr/share/java/confluent-common/*:/usr/share/java/kafka-serde-tools/*:/usr/share/java/monitoring-interceptors/*:/usr/share/java/ignite-kafka-connector-ignite-2.14.0/*:/usr/bin/../share/java/kafka/*:/usr/bin/../share/java/confluent-telemetry/* -javaagent:/opt/prometheus/jmx_prometheus_javaagent.jar=8077:/opt/prometheus/kafka_connect.yml org.apache.kafka.connect.cli.ConnectDistributed /etc/kafka/connect-distributed.properties

关键错误 #

Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.apache.ignite.internal.util.IgniteUtils

类存在验证 #

$ jar -tf ignite-core-2.14.0.jar | grep -i igniteutils.class
org/apache/ignite/internal/util/IgniteUtils.class

完整错误日志 #

[2023-05-05 09:55:16,083] INFO [ignite-eps-shared:cache-betradar.2.kafka-topic:dr-ignite-betradar|worker] Instantiated connector ignite-eps-shared:cache-betradar.2.kafka-topic:dr-ignite-betradar with version 7.2.1-ccs of type class org.apache.ignite.stream.kafka.connect.IgniteSourceConnector (org.apache.kafka.connect.runtime.Worker:274)
[2023-05-05 09:55:16,083] INFO [ignite-eps-shared:cache-betradar.2.kafka-topic:dr-ignite-betradar|worker] Finished creating connector ignite-eps-shared:cache-betradar.2.kafka-topic:dr-ignite-betradar (org.apache.kafka.connect.runtime.Worker:299)
[2023-05-05 09:55:16,085] ERROR [ignite-eps-shared:cache-betradar.2.kafka-topic:dr-ignite-betradar|task-0] Failed to start task ignite-eps-shared:cache-betradar.2.kafka-topic:dr-ignite-betradar-0 (org.apache.kafka.connect.runtime.Worker:549)
org.apache.kafka.connect.errors.ConnectException: Instantiation error
    at org.apache.kafka.connect.runtime.isolation.Plugins.newPlugin(Plugins.java:80)
    at org.apache.kafka.connect.runtime.isolation.Plugins.newConverter(Plugins.java:286)
    at org.apache.kafka.connect.runtime.Worker.startTask(Worker.java:521)
    at org.apache.kafka.connect.runtime.distributed.DistributedHerder.startTask(DistributedHerder.java:1421)
    at org.apache.kafka.connect.runtime.distributed.DistributedHerder.lambda$getTaskStartingCallable$22(DistributedHerder.java:1434)
    at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
    at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: org.apache.kafka.common.KafkaException: Could not instantiate class org.apache.ignite.stream.kafka.connect.serialization.CacheEventConverter
    at org.apache.kafka.common.utils.Utils.newInstance(Utils.java:396)
    at org.apache.kafka.connect.runtime.isolation.Plugins.newPlugin(Plugins.java:78)
    ... 8 more
Caused by: java.lang.reflect.InvocationTargetException
    at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77)
    at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499)
    at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480)
    at org.apache.kafka.common.utils.Utils.newInstance(Utils.java:392)
    ... 9 more
Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.apache.ignite.internal.util.IgniteUtils
    at org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.<init>(AbstractNodeNameAwareMarshaller.java:36)
    at org.apache.ignite.marshaller.jdk.JdkMarshaller.<init>(JdkMarshaller.java:86)
    at org.apache.ignite.marshaller.jdk.JdkMarshaller.<init>(JdkMarshaller.java:80)
    at org.apache.ignite.marshaller.jdk.JdkMarshaller.<clinit>(JdkMarshaller.java:71)
    at org.apache.ignite.stream.kafka.connect.serialization.CacheEventDeserializer.<clinit>(CacheEventDeserializer.java:34)
    at org.apache.ignite.stream.kafka.connect.serialization.CacheEventConverter.<init>(CacheEventConverter.java:33)
    ... 15 more

问题分析 #

这个错误是类初始化失败，而非单纯的类找不到。JVM能定位到IgniteUtils的字节码，但在执行类的静态初始化逻辑（静态变量赋值、静态代码块）时抛出未捕获异常，最终导致类初始化失败。核心原因是：

• Ignite 2.14.0版本未适配Java 17的模块系统（JPMS），其内部使用的反射、访问内部API等操作在Java 17的严格权限控制下被阻断。
• Java 17对反射访问、模块导出的限制比Java 11更严格，Ignite的旧版本代码依赖的一些非公开API在Java 17中被封闭。

解决办法 #

1. 升级Ignite版本（推荐） #

Ignite 2.15.0及以上版本正式支持Java 17，直接升级到兼容版本：

• 替换现有ignite-core-2.14.0.jar为ignite-core-2.15.0.jar或更高版本
• 同步升级Ignite Kafka Connector的Jar包，确保版本一致

2. 添加Java 17权限放宽参数（临时方案） #

如果暂时无法升级，在Kafka Connect的启动命令中添加以下JVM参数，允许Ignite访问必要的内部API：

--add-opens java.base/java.lang=ALL-UNNAMED
--add-opens java.base/java.nio=ALL-UNNAMED
--add-opens java.base/java.util=ALL-UNNAMED
--add-opens java.base/java.util.concurrent=ALL-UNNAMED
--add-opens java.base/java.lang.reflect=ALL-UNNAMED
--add-exports java.base/sun.nio.ch=ALL-UNNAMED
--add-exports java.base/sun.security.action=ALL-UNNAMED

将这些参数插入到启动命令的Java参数区域，例如放在-Xmx2G之后。

3. 清理类路径重复项 #

启动命令中存在重复的Kafka类路径（/usr/share/java/kafka/*和/usr/bin/../share/java/kafka/*），可能导致类加载冲突。建议移除重复路径，确保Ignite的Jar包优先级正确。

4. 验证依赖完整性 #

检查Ignite所需的所有依赖Jar包是否齐全，Java 17下缺失依赖更容易触发类初始化失败。例如如果使用了Ignite的Spring整合、索引功能，需确保对应的ignite-spring.jar、ignite-indexing.jar等已加入类路径。

内容的提问来源于stack exchange，提问作者Milan Masek