tomcat进程意外退出的问题分析

一个运行几天的服务突然在昨天报错

15-May-2019 18:53:38.600 INFO [Thread-6] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio-10582"]

15-May-2019 18:53:40.649 INFO [Thread-6] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["ajp-nio-10583"]

15-May-2019 18:53:40.699 INFO [Thread-6] org.apache.catalina.core.StandardService.stopInternal Stopping service Catalina

15-May-2019 18:53:46.400 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoader.clearReferencesJdbc The web application [/weatherServer] registered the JDBC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

15-May-2019 18:53:46.401 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoader.clearReferencesThreads The web application [/weatherServer] appears to have started a thread named [Abandoned connection cleanup thread] but has failed to stop it. This is very likely to create a memory leak.

15-May-2019 18:53:46.401 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoader.clearReferencesThreads Stack trace of thread "Abandoned connection cleanup thread":

 java.lang.Object.wait(Native Method)

 java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:144)

 com.mysql.jdbc.AbandonedConnectionCleanupThread.run(AbandonedConnectionCleanupThread.java:43)

15-May-2019 18:53:46.401 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoader.clearReferencesThreads The web application [/weatherServer] appears to have started a thread named [commons-pool-EvictionTimer] but has failed to stop it. This is very likely to create a memory leak.

15-May-2019 18:53:46.401 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoader.clearReferencesThreads Stack trace of thread "commons-pool-EvictionTimer":

 

 

百度了好久，在这篇文章里面看到相关的结论

http://hongjiang.info/why-kill-2-cannot-stop-tomcat/

是不是这个问题，还需时间观察

因为刚好昨天下午18点45分下班，急匆匆把ssh关掉 然后18点53分就报了这个错