Frequent "Queued close did not succeed" errors

[ngc4579]

Hi,

we are utilizing the Strimzi Kafka Operator to orchestrate a Kafka cluster. All operators are frequently throwing exceptions like the following (a couple of times every minute).

2024-02-01 08:34:42 WARN  JdkWebSocketImpl:129 - Queued close did not succeed
java.lang.IllegalArgumentException: statusCode
	at jdk.internal.net.http.websocket.WebSocketImpl.sendClose(WebSocketImpl.java:309) ~[java.net.http:?]
	at io.fabric8.kubernetes.client.jdkhttp.JdkWebSocketImpl.sendClose(JdkWebSocketImpl.java:126) ~[io.fabric8.kubernetes-httpclient-jdk-6.9.2.jar:?]
	at io.fabric8.kubernetes.client.dsl.internal.WatcherWebSocketListener.onClose(WatcherWebSocketListener.java:67) ~[io.fabric8.kubernetes-client-6.9.2.jar:?]
	at io.fabric8.kubernetes.client.jdkhttp.JdkWebSocketImpl.onClose(JdkWebSocketImpl.java:84) ~[io.fabric8.kubernetes-httpclient-jdk-6.9.2.jar:?]
	at jdk.internal.net.http.websocket.WebSocketImpl$ReceiveTask.processClose(WebSocketImpl.java:528) ~[java.net.http:?]
	at jdk.internal.net.http.websocket.WebSocketImpl$ReceiveTask.run(WebSocketImpl.java:459) ~[java.net.http:?]
	at jdk.internal.net.http.common.SequentialScheduler$CompleteRestartableTask.run(SequentialScheduler.java:149) ~[java.net.http:?]
	at jdk.internal.net.http.common.SequentialScheduler$SchedulableTask.run(SequentialScheduler.java:230) ~[java.net.http:?]
	at jdk.internal.net.http.HttpClientImpl$DelegatingExecutor.execute(HttpClientImpl.java:157) ~[java.net.http:?]
	at jdk.internal.net.http.common.SequentialScheduler.runOrSchedule(SequentialScheduler.java:305) ~[java.net.http:?]
	at jdk.internal.net.http.common.SequentialScheduler.runOrSchedule(SequentialScheduler.java:274) ~[java.net.http:?]
	at jdk.internal.net.http.websocket.WebSocketImpl.trySetState(WebSocketImpl.java:845) ~[java.net.http:?]
	at jdk.internal.net.http.websocket.WebSocketImpl.signalClose(WebSocketImpl.java:771) ~[java.net.http:?]
	at jdk.internal.net.http.websocket.WebSocketImpl$SignallingMessageConsumer.onComplete(WebSocketImpl.java:828) ~[java.net.http:?]
	at jdk.internal.net.http.websocket.TransportImpl$ReceiveTask.run(TransportImpl.java:709) ~[java.net.http:?]
	at jdk.internal.net.http.common.SequentialScheduler$CompleteRestartableTask.run(SequentialScheduler.java:149) ~[java.net.http:?]
	at jdk.internal.net.http.common.SequentialScheduler$SchedulableTask.run(SequentialScheduler.java:230) ~[java.net.http:?]
	at jdk.internal.net.http.common.SequentialScheduler.runOrSchedule(SequentialScheduler.java:303) ~[java.net.http:?]
	at jdk.internal.net.http.common.SequentialScheduler.runOrSchedule(SequentialScheduler.java:256) ~[java.net.http:?]
	at jdk.internal.net.http.websocket.TransportImpl$ReadEvent.handle(TransportImpl.java:766) ~[java.net.http:?]
	at jdk.internal.net.http.RawChannelTube$ReadSubscriber.checkEvents(RawChannelTube.java:174) ~[java.net.http:?]
	at jdk.internal.net.http.RawChannelTube$ReadSubscriber.onComplete(RawChannelTube.java:223) ~[java.net.http:?]
	at jdk.internal.net.http.common.SSLTube$DelegateWrapper.onComplete(SSLTube.java:276) ~[java.net.http:?]
	at jdk.internal.net.http.common.SSLTube$SSLSubscriberWrapper.complete(SSLTube.java:440) ~[java.net.http:?]
	at jdk.internal.net.http.common.SSLTube$SSLSubscriberWrapper.onComplete(SSLTube.java:541) ~[java.net.http:?]
	at jdk.internal.net.http.common.SubscriberWrapper.checkCompletion(SubscriberWrapper.java:472) ~[java.net.http:?]
	at jdk.internal.net.http.common.SubscriberWrapper$DownstreamPusher.run1(SubscriberWrapper.java:334) ~[java.net.http:?]
	at jdk.internal.net.http.common.SubscriberWrapper$DownstreamPusher.run(SubscriberWrapper.java:259) ~[java.net.http:?]
	at jdk.internal.net.http.common.SequentialScheduler$LockingRestartableTask.run(SequentialScheduler.java:205) ~[java.net.http:?]
	at jdk.internal.net.http.common.SequentialScheduler$CompleteRestartableTask.run(SequentialScheduler.java:149) ~[java.net.http:?]
	at jdk.internal.net.http.common.SequentialScheduler$SchedulableTask.run(SequentialScheduler.java:230) ~[java.net.http:?]
	at jdk.internal.net.http.common.SequentialScheduler.runOrSchedule(SequentialScheduler.java:303) ~[java.net.http:?]
	at jdk.internal.net.http.common.SequentialScheduler.runOrSchedule(SequentialScheduler.java:256) ~[java.net.http:?]
	at jdk.internal.net.http.common.SubscriberWrapper.outgoing(SubscriberWrapper.java:232) ~[java.net.http:?]
	at jdk.internal.net.http.common.SSLFlowDelegate$Reader.processData(SSLFlowDelegate.java:513) ~[java.net.http:?]
	at jdk.internal.net.http.common.SSLFlowDelegate$Reader$ReaderDownstreamPusher.run(SSLFlowDelegate.java:268) ~[java.net.http:?]
	at jdk.internal.net.http.common.SequentialScheduler$LockingRestartableTask.run(SequentialScheduler.java:205) ~[java.net.http:?]
	at jdk.internal.net.http.common.SequentialScheduler$CompleteRestartableTask.run(SequentialScheduler.java:149) ~[java.net.http:?]
	at jdk.internal.net.http.common.SequentialScheduler$SchedulableTask.run(SequentialScheduler.java:230) ~[java.net.http:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
	at java.lang.Thread.run(Thread.java:840) ~[?:?]
2024-02-01 08:34:42 WARN  JdkWebSocketImpl:142 - Aborting WebSocket due to a write error or failure with sendClose

The call stack suggests the issue originates somewhere from inside the fabric8 Kubernetes client (version 6.9.2).

Does anyone have a clue what might cause this, or else any further hint as to where to start digging for the root cause?

(Kubernetes 1.27.6 hosted environment)

[Edit: issue still persists with K8s 1.28.5.]