JreMemoryLeakPreventionListener引发的报错问题
博客专区 > Tomax 的博客 > 博客详情
JreMemoryLeakPreventionListener引发的报错问题
Tomax 发表于1年前
JreMemoryLeakPreventionListener引发的报错问题
  • 发表于 1年前
  • 阅读 14
  • 收藏 0
  • 点赞 0
  • 评论 0

腾讯云 新注册用户 域名抢购1元起>>>   

摘要: Tomcat 6.0.25 之后引入防止内存泄露的机制JreMemoryLeakPreventionListener,停止tomcat服务时会把未成功回收的对象打印到日志中。

There is a memory leak detection feature introduced in Tomcat 6.0.25 that attempts to log objects that have failed to be unregistered by webapps it hosts when they are stopped, and were forcibly unregistered by Tomcat. As Tomcat is forcibly removing these objects, it is not a serious concern that these log messages occur.

停止tomcat服务后,报出以下错误:

严重: The web application [] appears to have started a thread named [Timer-0] but has failed to stop it. This is very likely to create a memory leak.
2016-9-27 21:33:48 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] appears to have started a thread named [pool-1-thread-1] but has failed to stop it. This is very likely to create a memory leak.
2016-9-27 21:33:48 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [] appears to have started a thread named [DefaultQuartzScheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak.
2016-9-27 21:33:48 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

初步诊断为服务停止时,线程池未能成功关闭,添加线程监听器ThreadListener,在服务停止的时候停止线程池:

public class ThreadListener implements ServletContextListener {

	private Log logger = LogFactory.getLog(ThreadListener.class);
	
	@Override
	public void contextInitialized(ServletContextEvent sce) {
		
	}

	@Override
	public void contextDestroyed(ServletContextEvent sce) {
		try {
			logger.info("销毁线程池");
			ProtoExecutorService.getExecutor().shutdownNow();
		} catch (Exception e) {
			logger.error(String.format("销毁线程池出错,错误信息:%s", e));
			e.printStackTrace();
		}
	}
}

继续运行一段时间后发现,停止tomcat服务后仍会出现同样报错,查找资料,http://stackoverflow.com/questions/5292349/is-this-very-likely-to-create-a-memory-leak-in-tomcat ,添加清理ThreadLocal的代码:

public class ThreadLocalImmolater {

	private Log logger = LogFactory.getLog(ThreadLocalImmolater.class);

	private static ThreadLocalImmolater immolater = null;
	
    Boolean debug;

    public ThreadLocalImmolater() {
        debug = false;
    }
    
    public synchronized static ThreadLocalImmolater getInstance(){
    	if(null == immolater){
    		immolater = new ThreadLocalImmolater();
    	}
    	return immolater;
    }
    
    public Integer immolate() throws Exception {
        int count = 0;
        final Field threadLocalsField = Thread.class.getDeclaredField("threadLocals");
        threadLocalsField.setAccessible(true);
        final Field inheritableThreadLocalsField = Thread.class.getDeclaredField("inheritableThreadLocals");
        inheritableThreadLocalsField.setAccessible(true);
        for (final Thread thread : Thread.getAllStackTraces().keySet()) {
            count += clear(threadLocalsField.get(thread));
            count += clear(inheritableThreadLocalsField.get(thread));
            
            if (thread != null) {
            	thread.setContextClassLoader(null);
            }
        }
        logger.info("immolated " + count + " values in ThreadLocals");
        return count;
    }

    private int clear(final Object threadLocalMap) throws Exception {
        if (threadLocalMap == null)
                return 0;
        int count = 0;
        final Field tableField = threadLocalMap.getClass().getDeclaredField("table");
        tableField.setAccessible(true);
        final Object table = tableField.get(threadLocalMap);
        for (int i = 0, length = Array.getLength(table); i < length; ++i) {
            final Object entry = Array.get(table, i);
            if (entry != null) {
                final Object threadLocal = ((WeakReference)entry).get();
                if (threadLocal != null) {
                    log(i, threadLocal);
                    Array.set(table, i, null);
                    ++count;
                }
            }
        }
        return count;
    }

    private void log(int i, final Object threadLocal) {
        if (!debug) {
            return;
        }
        if (threadLocal.getClass() != null &&
            threadLocal.getClass().getEnclosingClass() != null &&
            threadLocal.getClass().getEnclosingClass().getName() != null) {

            logger.info("threadLocalMap(" + i + "): " +
                        threadLocal.getClass().getEnclosingClass().getName());
        }
        else if (threadLocal.getClass() != null &&
                 threadLocal.getClass().getName() != null) {
            logger.info("threadLocalMap(" + i + "): " + threadLocal.getClass().getName());
        }
        else {
            logger.info("threadLocalMap(" + i + "): cannot identify threadlocal class name");
        }
    }

}

在ThreadListener中添加以下代码:

//清理线程
try {
	logger.info("清理线程");
	ThreadLocalImmolater.getInstance().immolate();
} catch (Exception e) {
	logger.error(String.format("清理线程出错,错误信息:%s", e));
	e.printStackTrace();
}

运行一段时间后发现,停止tomcat服务后不再出现同样错误,但是会出现

严重: The web application [] registered the JDBC driver [com.microsoft.sqlserver.jdbc.SQLServerDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

在ThreadListener中添加以下代码:

logger.info("关闭数据库连接");
Enumeration<Driver> drivers = DriverManager.getDrivers();
while (drivers.hasMoreElements()) {
	Driver driver = drivers.nextElement();
	try {
		DriverManager.deregisterDriver(driver);
		logger.info(String.format("deregistering jdbc driver: %s", driver));
	} catch (SQLException e) {
		logger.error(String.format("Error deregistering driver %s", driver), e);
	}

}

报错消失。

参考资料:

http://fourfireliu.iteye.com/blog/2187584

http://stackoverflow.com/questions/5292349/is-this-very-likely-to-create-a-memory-leak-in-tomcat

共有 人打赏支持
粉丝 0
博文 5
码字总数 4372
×
Tomax
如果觉得我的文章对您有用,请随意打赏。您的支持将鼓励我继续创作!
* 金额(元)
¥1 ¥5 ¥10 ¥20 其他金额
打赏人
留言
* 支付类型
微信扫码支付
打赏金额:
已支付成功
打赏金额: