PUBLIC - Liferay Portal Community Edition
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-11976

Clean threadlocal when undeploying portal to avoid potential threadlocal leaking

    Details

    • Type: Bug Bug
    • Status: Closed
    • Resolution: Fixed
    • Affects Version/s: 6.0.4 GA
    • Fix Version/s: 6.0.4 GA, 6.0.5 GA
    • Component/s: WCM
    • Labels:
      None
    • Similar Issues:
      Show 2 results 

      Description

      ThreadLocal leaking problem came up when upgrading tomcat to 6.0.26, when shutting down tomcat, there will be exceptions like:

      A web application created a ThreadLocal with key of type [null] and a value of type [java.lang.ref.WeakReference]
      but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed.

      For portal itself(excluding the third side library), if we suppose all clients use ThreadLocalFilter correctly, then it will not cause leaking problem.

      So, to avoid tomcat's error log, do cleaning as tomcat does when undeploying portal.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            SE Support
            Reporter:
            Tina Tian
            Recent user:
            Randy Zhu
            Participants of an Issue:
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Days since last comment:
              4 years, 51 weeks, 2 days ago

              Development

                Structure Helper Panel