Uploaded image for project: 'Grouper'
  1. Grouper
  2. GRP-1313

potential ws/ui memory leaks with threadlocals

    XMLWordPrintable

Details

    • Bug
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • None
    • 2.4.0, 2.3.0.patch
    • UI, WS
    • None
    • tomcat 6.0.26

    Description

      Note, I believe these are only if you reload the application in tomcat which is not recommended. If you shut down the application these should not be a problem. Not sure though.

      1.

      SEVERE: A web application created a ThreadLocal with key of type [java.lang.InheritableThreadLocal] (value [java.lang.InheritableThreadLocal@49f5a659]) and a value of type [edu.internet2.middleware.grouper.j2ee.GrouperRequestWrapper] (value [edu.internet2.middleware.grouper.j2ee.GrouperRequestWrapper@70124154]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed.

      2.

      May 27, 2016 5:01:13 PM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap
      SEVERE: A web application created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@567e768e]) and a value of type [edu.internet2.middleware.morphString.Crypto] (value [edu.internet2.middleware.morphString.Crypto@89990ff]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed.

      3.

      May 27, 2016 5:01:13 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
      SEVERE: A web application appears to have started a thread named [pool-2-thread-2] but has failed to stop it. This is very likely to create a memory leak.

      4.

      May 27, 2016 5:01:13 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
      SEVERE: A web application appears to have started a thread named [org.hibernate.cache.spi.UpdateTimestampsCache.data] but has failed to stop it. This is very likely to create a memory leak.

      5.

      May 27, 2016 5:01:13 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThread
      SEVERE: A web application appears to have started a TimerThread named [net.sf.ehcache.CacheManager@4c76ec2d] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.

      6.

      May 27, 2016 5:01:13 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
      SEVERE: A web application registered the JBDC driver [org.hsqldb.jdbc.JDBCDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

      7.

      May 27, 2016 5:01:13 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThread
      SEVERE: A web application appears to have started a TimerThread named [C3P0PooledConnectionPoolManager[identityToken->1lim7by9g1vgt9
      8x1kusjgc|1b778d0c]-AdminTaskTimer] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and
      hence the associated thread) has been forcibly cancelled.

      ComboPooledDataSource.reset() ?

      Attachments

        Activity

          People

            chris.hyzer@at.internet2.edu Chris Hyzer (upenn.edu)
            chris.hyzer@at.internet2.edu Chris Hyzer (upenn.edu)
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:

              Smart Checklist