Always clean the ThreadLocal variables.

最新推荐文章于 2022-03-11 17:57:02 发布

原创最新推荐文章于 2022-03-11 17:57:02 发布 · 234 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#java

java 同时被 3 个专栏收录

35 篇文章

订阅专栏

Tomcat

15 篇文章

订阅专栏

jboss

3 篇文章

订阅专栏

本文讨论了在使用STRUTS2框架时，如何在线程即将结束时手动清理ThreadLocal变量以防止内存泄漏。通过实现一个destroy()方法，确保在线程关闭时清理dispatcher和ActionContext变量。

Any variable stored in ThreadLocal are per thread as we knew, but most people does know that even the thread has been expeired or dead, it's copy of the variable in ThreadLocal won't disappear.

I read the STRUTS 2 code recently, figured out that you should always manually cleanup the variables in ThreadLocal when your thread is about to close.

In below code, ThreadLocal variables in dispatcher and ActionContext will be cleaned up:

    public void destroy() {
        if (dispatcher == null) {
            log.warn("something is seriously wrong, Dispatcher is not initialized (null) ");
        } else {
            try {
                dispatcher.cleanup();
            } finally {
                ActionContext.setContext(null);
            }
        }
    }

Just write this done in case forgot in future.