以下是我在 CentOS 机器上的 Catalina.out 文件中的唯一条目的摘录。我在 Spring 3 和我的应用程序中运行 Tomcat 6。有一大堆，所以我只选择了一些不断重复的。这种情况不会一直发生，但至少每周发生一次。

问题是我该怎么做才能防止波纹管发生？

Feb 3, 2011 2:37:48 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application [] registered the JBDC 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.

Feb 3, 2011 2:37:48 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [] appears to have started a thread named [com.iteezy.shared.domain.DirEntry.data] but has failed to stop it. This is very likely to create a memory leak.


Feb 3, 2011 2:37:48 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named

[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0] but has failed to stop it. This is very likely to create a memory leak.


Feb 3, 2011 2:37:48 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads  

SEVERE: The web application [] appears to have started a thread named [File Reaper] but has failed to stop it. This is very likely to create a memory leak.

Feb 3, 2011 2:37:48 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [] appears to have started a thread named [pool-1-thread-22] but has failed to stop it. This is very likely to create a memory leak.  

37:48 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
b application [] appears to have started a thread named 

[org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-2] but has failed to stop it. This is very likely to create a memory leak.

37:48 PM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap

b application [] created a ThreadLocal with key of type [net.sf.json.AbstractJSON$1] (value [net.sf.json.AbstractJSON$1@40bbb3d6]) and a value of type [java.util.HashSet] (value [[]]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.

最佳答案

当您定义一个外部标志时，线程应该在设置时进行轮询和退出 - 它必须是 volatile。否则该线程可能永远看不到其他线程所做的更改。

然而，在标准 API 中已经有类似的功能 - 它称为 interrupt() 方法和 Thread.currentThread().isInterrupted()。无需复制已经存在的逻辑。请参阅:Stopping a specific java thread .

据说在每个线程上调用 interrupt() 也是一个坏主意，因为不能保证所有线程都响应它。检查您的异常，我注意到以下线程未正确清理:

• com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0 - 关闭 C3P0 数据源。由于您使用的是 Spring，只需添加 destroy-method="close"。我们完成了这个线程。

• File Reaper - 据我所知，这个线程是由 FileCleaningTracker 创建的.您需要在关闭应用程序时显式调用 FileCleaningTracker.exitWhenFinished()(或者当不再需要该类时，我从未使用过它)或让 Spring 执行此操作(见上文)。有可能某些第 3 方库使用了它但未正确关闭 - 这意味着它存在错误。

• pool-1-thread-22 - 这是由 Executors 创建的线程之一内部实用程序 ExecutorService .确保在关闭期间对应用程序中的每个此类池调用 shutdown()。

• org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-2 - Quartz 工作线程(实际运行作业的线程)。 SchedulerFactoryBean 自动为您关闭调度程序，我认为 Tomcat 在这里弄错了，我也经常看到这个错误。不过看起来将 SchedulerFactoryBean.waitForJobsToCompleteOnShutdown 设置为 true 可以解决这个问题。

• com.iteezy.shared.domain.DirEntry.data - 我不确定这个。它要么是您自己的线程需要在关闭时被中断，要么是 H2 数据库线程(？)它的堆栈需要被检查以猜测它来自哪里。

底线是:不要只是杀死所有移动的东西(实际上，Tomcat 会在发出此警告后为您执行此操作)但要确定线程来自何处并使用特定于框架/库的 close() 方法以允许进一步清理。温柔一点。

关于java - Tomcat 6 内存泄漏日志条目，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/4899205/