Uploaded image for project: 'VIVO'
  1. VIVO
  2. VIVO-987

Fix "memory leak" messages at shutdown

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: v1.8
    • Component/s: None
    • Labels:
      None
    • Attachments:
      0
    • Comments:
      1

      Description

      How can we stop these messages?

      ==> catalina.out <==
      Mar 09, 2015 11:34:11 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
      SEVERE: The web application [/vivo] registered the JDBC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
      Mar 09, 2015 11:34:11 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
      SEVERE: The web application [/vivo] appears to have started a thread named [Abandoned connection cleanup thread] but has failed to stop it. This is very likely to create a memory leak.
      Mar 09, 2015 11:34:11 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
      SEVERE: The web application [/vivo] appears to have started a thread named [C3P0PooledConnectionPoolManager-AdminTaskTimer] but has failed to stop it. This is very likely to create a memory leak.
      Mar 09, 2015 11:34:11 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
      SEVERE: The web application [/vivo] appears to have started a thread named C3P0PooledConnectionPoolManager-Helper Thread-#0 but has failed to stop it. This is very likely to create a memory leak.
      Mar 09, 2015 11:34:11 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
      SEVERE: The web application [/vivo] appears to have started a thread named C3P0PooledConnectionPoolManager-Helper Thread-#1 but has failed to stop it. This is very likely to create a memory leak.
      Mar 09, 2015 11:34:11 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
      SEVERE: The web application [/vivo] appears to have started a thread named C3P0PooledConnectionPoolManager-Helper Thread-#2 but has failed to stop it. This is very likely to create a memory leak.
      Mar 09, 2015 11:34:11 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
      SEVERE: The web application [/vivo] appears to have started a thread named C3P0PooledConnectionPoolManager-Helper Thread-#3 but has failed to stop it. This is very likely to create a memory leak.
      Mar 09, 2015 11:34:11 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
      SEVERE: The web application [/vivo] appears to have started a thread named C3P0PooledConnectionPoolManager-Helper Thread-#4 but has failed to stop it. This is very likely to create a memory leak.
      Mar 09, 2015 11:34:11 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
      SEVERE: The web application [/vivo] appears to have started a thread named C3P0PooledConnectionPoolManager-Helper Thread-#5 but has failed to stop it. This is very likely to create a memory leak.
      Mar 09, 2015 11:34:11 AM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
      SEVERE: The web application [/vivo] created a ThreadLocal with key of type [com.hp.hpl.jena.tdb.transaction.DatasetGraphTransaction.ThreadLocalBoolean] (value [com.hp.hpl.jena.tdb.transaction.DatasetGraphTransaction$ThreadLocalBoolean@5ae7e9a9]) and a value of type [java.lang.Boolean] (value [false]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
      Mar 09, 2015 11:34:11 AM org.apache.coyote.AbstractProtocol stop

        Attachments

          Activity

            People

            • Assignee:
              j2blake Jim Blake
              Reporter:
              j2blake Jim Blake
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: