我有这些代码用于关闭c3p0连接管理器,但似乎还有一个未关闭的线程。我错过了什么吗?
Oct 11, 2016 5:12:09 PM org.springframework.context.support.AbstractApplicationContext doClose
INFO: Closing WebApplicationContext for namespace 'dispatcherServlet-servlet': startup date [Tue Oct 11 17:11:58 PHT 2016]; parent: Root WebApplicationContext
2016-10-11 17:12:09 - [INFO ] CRMContextListener - Trying to Close
2016-10-11 17:12:09 - [INFO ] CRMContextListener - Close Success
Oct 11, 2016 5:12:09 PM org.springframework.context.support.AbstractApplicationContext doClose
INFO: Closing Root WebApplicationContext: startup date [Tue Oct 11 17:11:44 PHT 2016]; root of context hierarchy
Oct 11, 2016 5:12:09 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: A web application registered the JBDC driver [oracle.jdbc.OracleDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered. Oct 11, 2016 5:12:09 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: A web application appears to have started a thread named [C3P0PooledConnectionPoolManager[identityToken->2xjsis9j1do3mrp1m3tqb8|fb6fd9c]-DeferredStatementDestroyerThread-#0] but has failed to stop it. This is very likely to create a memory leak.
这是我的servlet监听器的代码
public void contextDestroyed(ServletContextEvent sce) {
logger.info("Trying to Close");
for (Object o : C3P0Registry.getPooledDataSources()) {
try {
((PooledDataSource) o).close();
} catch (Exception e) {
logger.info("No thread was open...");
}
}
logger.info("Close Success");
}
这是我对c3p0 xml的配置
<bean id="dataSource" class="com.mchange.v2.c3p0.ComboPooledDataSource" destroy-method="close">
<property name="driverClass" value="oracle.jdbc.driver.OracleDriver" />
<property name="jdbcUrl" value="jdbc:oracle:thin:@sph-pdc-vm 1042:1521:DEV" />
<property name="user" value="TSW" />
<property name="password" value="TSW2015#" />
<property name="minPoolSize" value="2" />
<property name="maxPoolSize" value="20" />
<property name="initialPoolSize" value="5" />
<property name="testConnectionOnCheckin" value="true" />
<property name="idleConnectionTestPeriod" value="100" />
<property name="maxIdleTimeExcessConnections" value="5" />
<property name="maxStatementsPerConnection" value="10" />
<property name="acquireIncrement" value="1" />
<property name="statementCacheNumDeferredCloseThreads" value="1" />
<property name="acquireRetryAttempts" value="2" />
<property name="acquireRetryDelay" value="2000" />
</bean>
提前致谢....
答案 0 :(得分:2)
这可能不是真正的内存泄漏,而是误报,因为c3p0的线程花了一些时间来关闭,close()
不等待它完成,它是异步的。所以你有一个烦人的消息。请参阅this github issue,感谢github上的BuğraGedik。如果你想测试这个理论,你可能会增加一秒左右的延迟[即在致电Thread.sleep(1000)
后致电close()
},看看消息是否消失。
虽然我认为这不是您的问题,但您可以考虑添加一些Tomcat参数,以确保尝试关闭()线程始终成功。只需添加...
<property name="privilegeSpawnedThreads" value="true" />
<property name="contextClassLoaderSource" value="library" />
请参阅c3p0's docs。