Petals View

memory leak message from tomcat

Details

  • Type: Improvement Request Improvement Request
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: 1.2
  • Fix Version/s: None
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    Every time we stop the tomcat, we've got this message:

    GRAVE: The web application [/petals-view-ui] registered the JBDC driver [org.h2.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    1 oct. 2010 15:09:14 org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
    GRAVE: The web application [/petals-view-ui] registered the JBDC driver [org.postgresql.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    1 oct. 2010 15:09:14 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
    GRAVE: The web application [/petals-view-ui] appears to have started a thread named [H2 File Lock Watchdog /users/petalsgui/test/db/petalsview.lock.db] but has failed to stop it. This is very likely to create a memory leak.
    1 oct. 2010 15:09:14 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
    GRAVE: The web application [/petals-view-ui] appears to have started a thread named [H2 Log Writer PETALSVIEW] but has failed to stop it. This is very likely to create a memory leak.

    Is tomcat dummy? I don't think. So maybe there are some thread closings badly implemented...
    Put this track as minor?

    Show
    Every time we stop the tomcat, we've got this message: GRAVE: The web application [/petals-view-ui] registered the JBDC driver [org.h2.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered. 1 oct. 2010 15:09:14 org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc GRAVE: The web application [/petals-view-ui] registered the JBDC driver [org.postgresql.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered. 1 oct. 2010 15:09:14 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads GRAVE: The web application [/petals-view-ui] appears to have started a thread named [H2 File Lock Watchdog /users/petalsgui/test/db/petalsview.lock.db] but has failed to stop it. This is very likely to create a memory leak. 1 oct. 2010 15:09:14 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads GRAVE: The web application [/petals-view-ui] appears to have started a thread named [H2 Log Writer PETALSVIEW] but has failed to stop it. This is very likely to create a memory leak. Is tomcat dummy? I don't think. So maybe there are some thread closings badly implemented... Put this track as minor?
  • Environment:
    tomcat 6, jdk 1.6, RHEL 5

Issue Links

Activity

People

Dates

  • Created:
    Fri, 1 Oct 2010 - 15:14:21 +0200
    Updated:
    Mon, 8 Nov 2010 - 15:26:50 +0100