You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I created a job.batch and used Wait. pool() to monitor the running status of the pod created by my job. batch, when pod.status.phase is "Succeeded", save full logs and exit. But my main function does not exit, I try use jconsole to monitor my jvm, I found that one thread pool was not destroyed. I use a NamedThreadFactory to init ScheduledExecutorService, it is indeed this thread pool.
Describe the bug
I created a job.batch and used Wait. pool() to monitor the running status of the pod created by my job. batch, when pod.status.phase is "Succeeded", save full logs and exit. But my main function does not exit, I try use jconsole to monitor my jvm, I found that one thread pool was not destroyed. I use a NamedThreadFactory to init ScheduledExecutorService, it is indeed this thread pool.
Client Version
19.0.0
Kubernetes Version
1.27.0
Java Version
Java 17
To Reproduce
Expected behavior
I use
executorService.shutdown();
to destory the thread pool, the problem has been resolved. This is my code, I added a finally code block.Server (please complete the following information):
Additional context
This is my jvm thread dumps, if don't use
executorService.shutdown();
The text was updated successfully, but these errors were encountered: