简体   繁体   English

服务器由于[Pool-Cleaner]:Tomcat连接池而停止响应,但未能停止它。 这很可能造成内存泄漏

[英]Server Stop responding because of [Pool-Cleaner]:Tomcat Connection Pool but has failed to stop it. This is very likely to create a memory leak

Problem: 问题:

org.apache.catalina.loader.WebappClassLoader - The web application [/…] appears to have started a thread named [[Pool-Cleaner]:Tomcat Connection Pool[...] but has failed to stop it. org.apache.catalina.loader.WebappClassLoader-Web应用程序[/…]似乎已启动名为[[Pool-Cleaner]:Tomcat Connection Pool [...]]的线程,但未能停止该线程。 This is very likely to create a memory leak. 这很可能造成内存泄漏。

I have few application deployed in a tomcat server(tomcat-7.0.23) with jdk1.6.0_45 and the server i register with apache webserver. 我在jdk1.6.0_45的tomcat服务器(tomcat-7.0.23)中部署了一些应用程序,并且我在apache webserver中注册了该服务器。 After staring the server it is working fine until i get the above error for all the application separately all of a sudden and after that my tomcat giving 404 for all request but the tomcat process is still up and in browser it shows "FILE NOT FOUND". 盯着服务器后,它工作正常,直到突然我得到所有应用程序的上述错误,然后我的tomcat给出了404的所有请求,但是tomcat进程仍在运行,并且在浏览器中显示“找不到文件” 。

we use Tomcat connection pool with following configuration: 我们使用具有以下配置的Tomcat连接池:

<Resource 
name="Project1" 
auth="Container" 
type="javax.sql.DataSource" 
factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" 
url="DatabaseName" 
username="_username" 
password="_Password" 
driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver" 
initialSize="40"
maxActive="300" 
maxIdle="250" 
minIdle="90"
maxWait="10000" 
minEvictableIdleTimeMillis="300000" 
timeBetweenEvictionRunsMillis="120000"
validationInterval="30000"
validationQuery="SELECT 1" 
testOnBorrow="true" 
logAbandoned="true"
removeAbandoned="true" 
removeAbandonedTimeout="60" 
abandonWhenPercentageFull="50"
jdbcInterceptors="ResetAbandonedTimer"
/>

And the configuration is in context.xml file. 并且配置在context.xml文件中。

That memory leak warning is correct. 该内存泄漏警告是正确的。 It refers to a known issue in Tomcat 7.0.x that was fixed a few weeks ago ( r1744702 ) and will be included in 7.0.70 onwards. 它指的是Tomcat 7.0.x中的一个已知问题,该问题已在几周前修复( r1744702 ),并将自7.0.70起包含。

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 Tomcat jdbc 连接池 - Pool-Cleaner 内存泄漏 - Tomcat jdbc connection pool - Pool-Cleaner Memory Leak 该Web应用程序似乎已启动一个名为的线程,但未能停止该线程。 这很可能造成内存泄漏 - The web application appears to have started a thread named but has failed to stop it. This is very likely to create a memory leak Web应用程序似乎已启动名为[22]的线程但未能阻止它。 这很可能造成内存泄漏 - A web application appears to have started a thread named [22] but has failed to stop it. This is very likely to create a memory leak 无法停止辅助线程,可能会导致内存泄漏。 - Failed to stop the worker thread, likely to create a Memory leak. Servlet“已启动一个线程但未能阻止它” - Tomcat中的内存泄漏 - Servlet “has started a thread but failed to stop it” - memory leak in Tomcat Tomcat部署显示以下错误-很可能造成内存泄漏 - Tomcat Deployment shows the below error - Very likely to create a memory leak DBCP Tomcat连接池泄漏 - DBCP Tomcat connection pool leak c3p0连接池内存泄漏重新部署tomcat - c3p0 Connection pool memory leak redeploy tomcat 关闭 tomcat 时,我遇到了 [commons-pool-EvictionTimer] 但未能阻止它 - When shut down tomcat i met [commons-pool-EvictionTimer] but has failed to stop it Tomcat webapp错误-应用程序启动了线程[AWT-Windows],但未能将其停止-内存泄漏? - Tomcat webapp error - application started thread [AWT-Windows] but has failed to stop it - memory leak?
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM