tomcat关闭时未防止内存泄漏，JDBC强制注销及线程未停止警告，附项目启动时初始化druid物理连接

最新推荐文章于 2025-05-06 22:26:08 发布

Lk_Life

最新推荐文章于 2025-05-06 22:26:08 发布

阅读量3.8k

点赞数 1

分类专栏：遇到的问题

本文链接：https://blog.youkuaiyun.com/weixin_43574957/article/details/102981361

版权

本文介绍了在Tomcat关闭时如何预防内存泄漏，特别是针对JDBC连接，强调了强制注销和停止线程的重要性。同时，分享了在项目启动时如何初始化Druid物理连接的方法，以确保数据库连接的正确管理和释放。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

08-Nov-2019 22:37:57.028 警告 [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ROOT] registered the JDBC driver [com.alibaba.druid.proxy.DruidDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
08-Nov-2019 22:37:57.029 警告 [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread named [Druid-ConnectionPool-Create-17551093] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
 com.alibaba.druid.pool.DruidDataSource$CreateConnectionThread.run(DruidDataSource.java:2690)