KubernetesClient seems to run forever after migrating to kubernetes-httpclient-vertx

[rohanKanojia]

I was migrating one of my demo projects to use io.fabric8:kubernetes-httpclient-vertx.

After migration, programs seem to run forever. If I run a simple demo (e.g. CanITest.java ), the program appears to hang until I stop it myself:

kubernetes-client-demo : $ time mvn exec:java -Dexec.mainClass=io.fabric8.CanITest
[INFO] Scanning for projects...
[INFO] 
[INFO] -----------------< io.fabric8:kubernetes-client-demo >------------------
[INFO] Building kubernetes-client-demo 1.0-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[INFO] 
[INFO] --- exec-maven-plugin:1.4.0:java (default-cli) @ kubernetes-client-demo ---
Allowed: true
^C
real	10m21.025s
user	0m10.063s
sys	0m0.693s

This wasn't the case when I was using the default okhttp client. If I run the same program with default okhttp client, program terminates within 17s:

kubernetes-client-demo : $ mvn clean instatime mvn exec:java -Dexec.mainClass=io.fabric8.CanITest
[INFO] Scanning for projects...
[INFO] 
[INFO] -----------------< io.fabric8:kubernetes-client-demo >------------------
[INFO] Building kubernetes-client-demo 1.0-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[INFO] 
[INFO] --- exec-maven-plugin:1.4.0:java (default-cli) @ kubernetes-client-demo ---
Allowed: true
[WARNING] thread Thread[OkHttp ConnectionPool,5,io.fabric8.CanITest] was interrupted but is still alive after waiting at least 15000msecs
[WARNING] thread Thread[OkHttp ConnectionPool,5,io.fabric8.CanITest] will linger despite being asked to die via interruption
[WARNING] thread Thread[Okio Watchdog,5,io.fabric8.CanITest] will linger despite being asked to die via interruption
[WARNING] thread Thread[OkHttp Http2Connection,5,io.fabric8.CanITest] will linger despite being asked to die via interruption
[WARNING] NOTE: 3 thread(s) did not finish despite being asked to  via interruption. This is not a problem with exec:java, it is a problem with the running code. Although not serious, it should be remedied.
[WARNING] Couldn't destroy threadgroup org.codehaus.mojo.exec.ExecJavaMojo$IsolatedThreadGroup[name=io.fabric8.CanITest,maxpri=10]
java.lang.IllegalThreadStateException
    at java.lang.ThreadGroup.destroy (ThreadGroup.java:776)
    at org.codehaus.mojo.exec.ExecJavaMojo.execute (ExecJavaMojo.java:328)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:301)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:211)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:165)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:157)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:121)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:127)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:294)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:960)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  16.729 s
[INFO] Finished at: 2023-02-15T14:47:51+05:30
[INFO] ------------------------------------------------------------------------

real	0m17.669s
user	0m7.628s
sys	0m0.324s

Is there something I missed while migrating to io.fabric8:kubernetes-httpclient-vertx? I'm guessing this could be a configuration issue but not sure what I missed.

I've run this program on several demo classes. I see the same hanging behavior. It's not just in my demo project, If I modify kubernetes-examples to use kubernetes-httpclient-vertx and run some sample I see same behavior.