迁移至Jakarta后出现java.lang.NoClassDefFoundError: javax/activation/DataContentHandler问题排查

问题 #

原本使用javax.mail和javax.activation的模块已迁移至Jakarta环境，更新了所有依赖与导入语句，本地运行正常，但Docker容器中运行时出现以下错误：

java.lang.NoClassDefFoundError: javax/activation/DataContentHandler
    at java.base/java.lang.ClassLoader.defineClass1(Native Method)
    at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1027)
    at java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:150)
    at java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:862)
    at java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:760)
    at java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:681)
    at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:639)
    at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
    at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:526)
    at java.base/java.lang.ClassLoader.defineClass1(Native Method)
    at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1027)
    at java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:150)
    at java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:862)
    at java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:760)
    at java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:681)
    at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:639)
    at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
    at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:526)
    at jakarta.activation.MailcapCommandMap.getDataContentHandler(MailcapCommandMap.java:594)
    at jakarta.activation.MailcapCommandMap.createDataContentHandler(MailcapCommandMap.java:572)
    at jakarta.activation.CommandMap.createDataContentHandler(CommandMap.java:205)
    at jakarta.activation.DataHandler.getDataContentHandler(DataHandler.java:587)
    at jakarta.activation.DataHandler.getContent(DataHandler.java:514)
    at jakarta.mail.internet.MimeMessage.getContent(MimeMessage.java:1504)
    at org.assimbly.mail.component.mail.MailBinding.extractBodyFromMail(MailBinding.java:302)
    at org.assimbly.mail.component.mail.MailMessage.createBody(MailMessage.java:93)
    at org.apache.camel.support.MessageSupport.getBody(MessageSupport.java:68)
    at org.assimbly.mail.component.mail.MailConsumer.createExchange(MailConsumer.java:406)
    at org.assimbly.mail.component.mail.MailConsumer.retrieveMessages(MailConsumer.java:328)
    at org.assimbly.mail.component.mail.MailConsumer.poll(MailConsumer.java:164)
    at org.apache.camel.support.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:205)
    at org.apache.camel.support.ScheduledPollConsumer.run(ScheduledPollConsumer.java:119)
    at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
    at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:358)
    at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
    at java.base/java.lang.Thread.run(Thread.java:1583)
Caused by: java.lang.ClassNotFoundException: javax.activation.DataContentHandler
    at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
    at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
    at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:526)
    ... 38 common frames omitted

已检查依赖树未发现javax相关引用，Gradle中强制使用Jakarta依赖后问题仍存在，需定位仍调用javax的原因。

排查方案 #

• 检查Docker镜像中的实际依赖
  本地与Docker环境依赖可能存在差异，进入容器执行gradle dependencies查看依赖树，或直接解压容器内的应用jar包，执行jar -tf your-app.jar | grep javax搜索是否有javax相关类文件，确认是否有遗留的javax依赖混入。

• 排查SPI配置文件
  Jakarta Activation的MailcapCommandMap会通过SPI加载DataContentHandler，检查容器内META-INF/services/jakarta.activation.DataContentHandlerFactory内容是否指向javax实现；同时确认是否存在META-INF/services/javax.activation.DataContentHandlerFactory遗留文件，这类文件会触发旧javax类的加载。

• 精准排查隐性依赖
  部分第三方组件可能间接依赖旧javax包，可通过Gradle的dependencyInsight命令定位：

  ./gradlew dependencyInsight --dependency javax.activation --configuration runtimeClasspath
  

  也可输出容器运行时classpath的所有jar包，排查是否有javax相关包：

  echo $CLASSPATH | tr ':' '\n' | grep javax
  

• 验证编译打包一致性
  检查Dockerfile是否执行了clean build，避免缓存旧编译产物；同时在Gradle中明确排除javax依赖：

  configurations.all {
      exclude group: 'javax.activation', module: 'activation'
      exclude group: 'javax.mail', module: 'mail'
  }
  

• 检查JVM运行时参数
  容器启动时添加-verbose:class参数，输出所有类的加载来源，可直接定位javax.activation.DataContentHandler是否被加载及加载路径；同时检查是否设置了javax.activation.DataContentHandlerFactory系统属性，强制指向旧实现。

• 排查动态类加载/反射代码
  搜索业务代码或依赖库中是否存在反射加载javax类的逻辑，比如Class.forName("javax.activation.DataContentHandler")，这类调用不会在依赖树或导入语句中体现。

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