Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-6951

ClockDaemon very likely memory leak

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Neutral Neutral
    • None
    • 5.5.1
    • core
    • None
    • Tomcat 8.5.11, OpenJDK Runtime Environment (build 1.8.0_111-8u111-b14-2~bpo8+1-b14)

      A shutdown/redeploy of our production Magnolia 5.5.1 instance results in a large number of the following warning messages from Tomcat. This happens on the public and author instances.

      WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [magnoliaAuthor] appears to have started a thread named [Thread-46] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
  java.lang.Object.wait(Native Method)
  java.lang.Object.wait(Object.java:502)
  EDU.oswego.cs.dl.util.concurrent.ClockDaemon.nextTask(Unknown Source)
  EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(Unknown Source)
  java.lang.Thread.run(Thread.java:745)

      It seems that the EDU.oswego.cs.dl.util.concurrent.ClockDaemon#shutDown() is never being called from DelayedExecutor to clean-up these threads.

        Acceptance criteria

              Unassigned Unassigned
              rtenberge Ronald Ten Berge
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:

                  Bug DoR
                  Task DoD