我有一个Spring Boot应用程序,由于奇怪的限制,它需要每三个小时运行一次,并且不能在Quartz上运行,所以我一直在OS cron上每三个小时运行一次,完成后它就退出了。然而,在添加了micrometer registry-datadog(和spring-legacy)之后,它永远不会退出,它只是每隔20秒或任何默认时间段发送一次指标,即使在调用registry.close()之后也是如此。
我是注定要像荷兰人一样永远在处理的海洋中航行,还是我犯了一个明显的错误?
代码:它会到达SpringApplication.exit(ctx),但实际上并不能干净地退出。(服务是一个TimedExecutorService。)
public void close() throws InterruptedException {
service.shutdown();
service.awaitTermination(Long.MAX_VALUE, TimeUnit.NANOSECONDS);
meterRegistry.close();
SpringApplication.exit(ctx);
}发布于 2018-05-03 20:59:44
这听起来像是个bug。Datadog exporter可能正在非守护程序线程中运行。JVM将非守护进程线程视为应用程序关键工作。
因此,从本质上讲,JVM认为在非守护进程线程完成之前,它不应该关闭。在Datadog导出器线程的情况下,这可能不会发生。
要验证是否存在非守护程序线程,请使用jstack生成线程转储。(命令:jstack <pid>)或转储close方法中的所有线程:
ThreadMXBean threadMxBean = ManagementFactory.getThreadMXBean();
for (ThreadInfo ti : threadMxBean.dumpAllThreads(true, true)) {
System.out.print(ti.toString());
}下面是一个线程转储输出示例。请注意第一行中的单词“daemon”:
"pool-1-thread-1" #13 prio=5 os_prio=31 tid=0x00007fe885aa5000 nid=0xa907 waiting on condition [0x000070000d67b000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000006c07e9720> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1081)
at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)https://stackoverflow.com/questions/50148430
复制相似问题