On Apr 10, 3:01 pm, Jim <[email protected]> wrote: > I am using Tomcat 7.0.25 in a Linux machine > > I am using Tomcat's connection pool > (org.apache.tomcat.dbcp.dbcp.BasicDataSource). As database > I am using H2 as a file database. > All is ok, but I have the following problem. > On shutdown of Tomcat I see in catalina.out: > > SEVERE: The web application [/GeneralApplication] appears to have > started a thread named [H2 > Log Writer GENERICAPPLICATION] but has failed to stop it. This is very > likely to create a > memory leak. > Apr 4, 2012 2:32:54 PM org.apache.catalina.loader.WebappClassLoader > clearReferencesThreads > SEVERE: The web application [/GeneralApplication] appears to have > started a thread named [H2 > File Lock Watchdog /opt/en/repos/tomcat/webapps/GeneralApplication/db/ > internaldatabase.lock.db] > but has failed to stop it. This is very likely to create a memory > leak. > > After contacting Tomcat dev (thread here ) the problem seems to be in > H2 (specifically the classloader that H2's JDBC is using is not the > proper one i.e. the same class loader that loaded the JDBC driver). > The root cause is pointed out to be: > "H2 creates those threads it should ensure that the > context class loader for the threads is set to the same class loader > that loaded the JDBC driver. We had similar issues with the evictor > thread in Apache Commons Pool (used by DBCP)." > > Could you please look into this? > Is this a new issue. > I suspect that after the new memory leak detection mechanism > introduced in Tomcat 7, H2 will produce similar reports in all > installations
Link to discussion with tomcat dev: http://mail-archives.apache.org/mod_mbox/tomcat-users/201204.mbox/%[email protected]%3E -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
