Kubernetes Pod中双Java定时任务启动报错：httpclientconf已被占用

在Kubernetes Pod中同时运行两个基于同一Java应用jar包的定时任务，通过-Djob参数指定不同任务名，执行命令如下：

• java -Djob=jobX -jar application.jar
• java -Djob=jobY -jar application.jar

两个任务都需要调用外部服务的HTTP接口，但其中一个任务启动成功，另一个启动失败，抛出如下错误栈：

java.lang.ExceptionInInitializerError: null
at reactor.netty.http.client.HttpClient.lambda$request$12(HttpClient.java:1042)
~[reactor-netty-0.9.20.RELEASE.jar!/:0.9.20.RELEASE]
at reactor.netty.tcp.TcpClientBootstrap.configure(TcpClientBootstrap.java:39)
~[reactor-netty-0.9.20.RELEASE.jar!/:0.9.20.RELEASE]
at reactor.netty.tcp.TcpClientBootstrap.configure(TcpClientBootstrap.java:39)
~[reactor-netty-0.9.20.RELEASE.jar!/:0.9.20.RELEASE]
at reactor.netty.tcp.TcpClientBootstrap.configure(TcpClientBootstrap.java:39)
~[reactor-netty-0.9.20.RELEASE.jar!/:0.9.20.RELEASE]
at reactor.netty.tcp.TcpClient.connect(TcpClient.java:212)~[reactor-netty-0.9.20.RELEASE.jar!/:0.9.20.RELEASE]
at reactor.netty.http.client.HttpClientFinalizer.connect(HttpClientFinalizer.java:80)~[reactor-netty-0.9.20.RELEASE.jar!/:0.9.20.RELEASE]
at reactor.netty.http.client.HttpClientFinalizer.responseConnection(HttpClientFinalizer.java:97)~[reactor-netty-0.9.20.RELEASE.jar!/:0.9.20.RELEASE]
at org.springframework.http.client.reactive.ReactorClientHttpConnector.connect(ReactorClientHttpConnector.java:112)~[spring-web-5.2.15.RELEASE.jar!/:5.2.15.RELEASE]
at org.springframework.web.reactive.function.client.ExchangeFunctions$DefaultExchangeFunction.exchange(ExchangeFunctions.java:104)~[spring-webflux-5.2.15.RELEASE.jar!/:5.2.15.RELEASE]
at org.springframework.web.reactive.function.client.DefaultWebClient$DefaultRequestBodyUriSpec.lambda$exchange$0(DefaultWebClient.java:338)~[spring-webflux-5.2.15.RELEASE.jar!/:5.2.15.RELEASE]
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:44)~[reactor-core-3.3.17.RELEASE.jar!/:3.3.17.RELEASE]
at reactor.core.publisher.Mono.subscribe(Mono.java:4252)~[reactor-core-3.3.17.RELEASE.jar!/:3.3.17.RELEASE]
at reactor.core.publisher.Mono.block(Mono.java:1684)~[reactor-core-3.3.17.RELEASE.jar!/:3.3.17.RELEASE]
at -- className and method
at org.springframework.boot.SpringApplication.callRunner(SpringApplication.java:)~[spring-boot-2.3.12.RELEASE.jar!/:2.3.12.RELEASE]
at org.springframework.boot.SpringApplication.callRunners(SpringApplication.java:)~[spring-boot-2.3.12.RELEASE.jar!/:2.3.12.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:319)~[spring-boot-2.3.12.RELEASE.jar!/:2.3.12.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1247)~[spring-boot-2.3.12.RELEASE.jar!/:2.3.12.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1236)~[spring-boot-2.3.12.RELEASE.jar!/:2.3.12.RELEASE]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_331]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_331]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_331]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_331]
at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:49)~[app.jar:0.0.56]
at org.springframework.boot.loader.Launcher.launch(Launcher.java:108)~[app.jar:0.0.56]
at org.springframework.boot.loader.Launcher.launch(Launcher.java:58)~[app.jar:0.0.56]
at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:88)~[app.jar:0.0.56]
Caused by:
java.lang.IllegalArgumentException: "httpclientconf" is already in use
at io.netty.util.ConstantPool.createOrThrow(ConstantPool.java:108)~[netty-common-4.1.65.Final.jar!/:4.1.65.Final]
at io.netty.util.ConstantPool.newInstance(ConstantPool.java:90)~[netty-common-4.1.65.Final.jar!/:4.1.65.Final]
at io.netty.util.AttributeKey.newInstance(AttributeKey.java:55)~[netty-common-4.1.65.Final.jar!/:4.1.65.Final]
at reactor.netty.http.client.HttpClientConfiguration.<clinit>(HttpClientConfiguration.java:51)
~[reactor-netty-0.9.20.RELEASE.jar!/:0.9.20.RELEASE]

原因 #

核心错误是"httpclientconf" is already in use，这是因为两个Java进程共享了Netty的全局ConstantPool实例。第二个进程初始化Reactor Netty的HttpClientConfiguration时，尝试创建名为httpclientconf的AttributeKey，但该Key已被第一个进程注册到全局池中，导致冲突抛出异常。

同一Pod的同一容器内运行多个JVM进程时，容易出现此类问题——它们共享系统类加载器空间，Netty的全局静态变量未做进程隔离。

解决办法 #

1. 用独立容器运行每个任务 #

不在同一个容器内运行两个JVM进程，而是为每个任务创建独立容器（或独立Pod），让每个进程拥有独立的类加载空间和全局变量，彻底避免资源冲突。

修改Pod配置示例：

apiVersion: v1
kind: Pod
metadata:
  name: job-pod
spec:
  containers:
  - name: job-x
    image: your-java-image
    command: ["java", "-Djob=jobX", "-jar", "application.jar"]
  - name: job-y
    image: your-java-image
    command: ["java", "-Djob=jobY", "-jar", "application.jar"]

2. 为每个进程指定独立Netty属性前缀 #

若必须在同一容器运行，可通过JVM参数让Netty使用不同属性前缀，确保每个进程的Key名称唯一。添加以下参数：

• 任务X：-Dio.netty.attributeKeyPrefix=jobX
• 任务Y：-Dio.netty.attributeKeyPrefix=jobY

修改后的执行命令：

• java -Dio.netty.attributeKeyPrefix=jobX -Djob=jobX -jar application.jar
• java -Dio.netty.attributeKeyPrefix=jobY -Djob=jobY -jar application.jar

3. 升级Reactor Netty版本 #

你使用的0.9.20.RELEASE版本存在全局变量未隔离的问题，升级到该分支的最新稳定版（或更高稳定分支）可能已修复此问题，重新打包应用即可。

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