关于C3P0 资源销毁时找不到 BasicResourcePool$1DestroyResourceTask 的填坑过程

最新推荐文章于 2024-07-23 17:06:43 发布

smht2598

最新推荐文章于 2024-07-23 17:06:43 发布

阅读量5.3k

点赞数 1

分类专栏： java tomcat c3p0

本文链接：https://blog.csdn.net/smht2598/article/details/81008435

版权

博客讲述了在C3P0升级到0.9.5.2版本后，仍然出现找不到BasicResourcePool$1DestroyResourceTask类的问题。作者发现原因是系统服务在销毁资源前已停止，而非C3P0版本问题。进一步排查发现，是由于用服人员忘记升级数据库脚本，导致解析MyBatis mapper文件失败，进而引发服务关闭。服务关闭后的定时线程尝试销毁资源时，因找不到类而抛出异常。

摘要由CSDN通过智能技术生成

现场运维人员升级版本之后，十万火急的求救 -- 系统启动不了了。看了下日志：

SEVERE: The web application [/launcherM] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] but has failed to stop it. This is very likely to create a memory leak.
Jul 11, 2018 2:51:22 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/launcherM] 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.
Jul 11, 2018 2:51:22 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/launcherM] appears to have started a thread named [MySQL Statement Cancellation Timer] but has failed to stop it. This is very likely to create a memory leak.
Jul 11, 2018 2:51:22 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Jul 11,