springboot 项目在本地启动正常，maven打包运行包如下错误，在项目中去掉 @KafkaListener注解打包运行不会报错，怀疑是jar依赖的问题，求解！

Question

[2019-11-25 14:53:48.299][main][KEY:] INFO- Stopping service [Tomcat] -[org.apache.juli.logging.DirectJDKLog:log] [DirectJDKLog.java:180]
[2019-11-25 14:53:48.499][localhost-startStop-2][KEY:] WARN- The web application [ROOT] appears to have started a thread named [logback-1] but ha
s failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
java.base@11.0.3/jdk.internal.misc.Unsafe.park(Native Method)
java.base@11.0.3/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:234)
java.base@11.0.3/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2123)
java.base@11.0.3/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1182)
java.base@11.0.3/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)
java.base@11.0.3/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1054)
java.base@11.0.3/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1114)
java.base@11.0.3/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
java.base@11.0.3/java.lang.Thread.run(Thread.java:834) -[org.apache.juli.logging.DirectJDKLog:log] [DirectJDKLog.java:180]
[2019-11-25 14:53:48.503][localhost-startStop-2][KEY:] WARN- The web application [ROOT] appears to have started a thread named [Timer-0] but has
failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
java.base@11.0.3/java.lang.Object.wait(Native Method)
java.base@11.0.3/java.util.TimerThread.mainLoop(Timer.java:553)
java.base@11.0.3/java.util.TimerThread.run(Timer.java:506) -[org.apache.juli.logging.DirectJDKLog:log] [DirectJDKLog.java:180]
[2019-11-25 14:53:48.504][localhost-startStop-2][KEY:] WARN- The web application [ROOT] appears to have started a thread named [com.alibaba.nacos
.naming.client.listener] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
java.base@11.0.3/jdk.internal.misc.Unsafe.park(Native Method)
java.base@11.0.3/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:234)
java.base@11.0.3/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2123)
java.base@11.0.3/java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:458)
com.alibaba.nacos.client.naming.core.EventDispatcher$Notifier.run(EventDispatcher.java:114)
java.base@11.0.3/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
java.base@11.0.3/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
java.base@11.0.3/java.lang.Thread.run(Thread.java:834) -[org.apache.juli.logging.DirectJDKLog:log] [DirectJDKLog.java:180]
[2019-11-25 14:53:48.508][localhost-startStop-2][KEY:] WARN- The web application [ROOT] appears to have started a thread named [com.alibaba.nacos
.naming.beat.sender] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
java.base@11.0.3/jdk.internal.misc.Unsafe.park(Native Method)
java.base@11.0.3/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:234)
java.base@11.0.3/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2123)
java.base@11.0.3/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1182)
java.base@11.0.3/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)
java.base@11.0.3/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1054)
java.base@11.0.3/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1114)
java.base@11.0.3/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
java.base@11.0.3/java.lang.Thread.run(Thread.java:834) -[org.apache.juli.logging.DirectJDKLog:log] [DirectJDKLog.java:180]
[2019-11-25 14:53:48.514][localhost-startStop-2][KEY:] WARN- The web application [ROOT] appears to have started a thread named [com.alibaba.nacos
.naming.beat.sender] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
java.base@11.0.3/jdk.internal.misc.Unsafe.park(Native Method)
java.base@11.0.3/java.util.concurrent.locks.LockSupport.park(LockSupport.java:194)
java.base@11.0.3/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2081)
java.base@11.0.3/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1177)
java.base@11.0.3/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)
java.base@11.0.3/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1054)
java.base@11.0.3/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1114)
java.base@11.0.3/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
java.base@11.0.3/java.lang.Thread.run(Thread.java:834) -[org.apache.juli.logging.DirectJDKLog:log] [DirectJDKLog.java:180]
[2019-11-25 14:53:48.525][localhost-startStop-2][KEY:] WARN- The web application [ROOT] appears to have started a thread named [com.alibaba.nacos
.naming.failover] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
java.base@11.0.3/jdk.internal.misc.Unsafe.park(Native Method)
java.base@11.0.3/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:234)
java.base@11.0.3/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2123)
java.base@11.0.3/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1182)
java.base@11.0.3/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)
java.base@11.0.3/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1054)
java.base@11.0.3/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1114)
java.base@11.0.3/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
java.base@11.0.3/java.lang.Thread.run(Thread.java:834) -[org.apache.juli.logging.DirectJDKLog:log] [DirectJDKLog.java:180]
[2019-11-25 14:53:48.531][localhost-startStop-2][KEY:] WARN- The web application [ROOT] appears to have started a thread named [com.alibaba.nacos
.naming.push.receiver] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
java.base@11.0.3/java.net.DualStackPlainDatagramSocketImpl.socketReceiveOrPeekData(Native Method)
java.base@11.0.3/java.net.DualStackPlainDatagramSocketImpl.receive0(DualStackPlainDatagramSocketImpl.java:124)
java.base@11.0.3/java.net.AbstractPlainDatagramSocketImpl.receive(AbstractPlainDatagramSocketImpl.java:181)
java.base@11.0.3/java.net.DatagramSocket.receive(DatagramSocket.java:814)
java.base@11.0.3/java.net.AbstractPlainDatagramSocketImpl.receive(AbstractPlainDatagramSocketImpl.j
java.base@11.0.3/java.net.DatagramSocket.receive(DatagramSocket.java:814)
com.alibaba.nacos.client.naming.core.PushReceiver.run(PushReceiver.java:73)
java.base@11.0.3/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
java.base@11.0.3/java.util.concurrent.FutureTask.run(FutureTask.java:264)
java.base@11.0.3/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Scheduled
java.base@11.0.3/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
java.base@11.0.3/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
java.base@11.0.3/java.lang.Thread.run(Thread.java:834) -[org.apache.juli.logging.DirectJDKLog:log]

Answer 1

启动了一个nacos的处理线程但是没有关闭，有可能是这个线程处理的东西没处理完，或者资源被其他资源占用比如cpu一直没分配到，没获取到锁资源，或是内存不足等情况