Uploaded image for project: 'Log4j 2'
  1. Log4j 2
  2. LOG4J2-1164

Configuration watch thread causes Tomcat memory leak

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.5
    • Fix Version/s: 2.5
    • Component/s: Configurators
    • Labels:
      None

      Description

      While investigating LOG4J2-1159 I found that Tomcat (7.0.50) now gives this output when I shut it down while the test webapp is deployed:

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

      This thread is probably the ScheduledExecutor that is now started if monitorInterval > 0. Still checking why the app is not stopped() and the executor is not shut down...

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                rpopma Remko Popma
                Reporter:
                rpopma Remko Popma
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: