Hi Thomas, I took thread dumps of this and the "H2 File Lock Watchdog" remains hanging *after *Tomcat has been shutdown. As a result the JVM does not shutdown either. Does H2 start this thread as non-daemon perhaps? Anyway the complaint of the memory leak is about the "H2 File Lock Watchdog" and I see that it is the Filewatch dog that remains hanging. And yes if I delete the lock.db file it is recreated. I guess by H2? How can this be resolved? I am stuck now. Could you please help me?
Am Freitag, 22. Juni 2012 16:19:49 UTC+3 schrieb Thomas Mueller: > > Hi, > > In my previous mail I asked "What happens if you delete this file?" - > so what happens? > > I understand the connection is not closed when the *web application* is > stopped. > > But the connection should be closed (by Tomcat) if *Tomcat* is stopped. > > Regards, > Thomas > > > On Fri, Jun 22, 2012 at 11:02 AM, Jim <[email protected]> wrote: > > Hi Thomas, > > I think that the problem of the remaining lock.db file is caused by the > > problem discussed by the thread. > > The problem is that when I shut down tomcat the web application is > shutdown > > first but due to the way H2 driver is loaded (as discussed in the Tomcat > > thread) the pool is not being disposed of by Tomcat at that point and > hence > > the problem appears (since H2 has open connections). This is an > interaction > > of H2 driver with Tomcat > > So I can't figure out what you mean that "the database stays open, > that's > > correct and OK. " > > > > > > Am Donnerstag, 21. Juni 2012 22:41:15 UTC+3 schrieb Thomas Mueller: > >> > >> Hi, > >> > >> > I stop Tomcat using $CATALINA_HOME/bin/shutdown.sh and I occusionally > >> > expererience that the .lock.db file is not deleted. > >> > >> What happens if you delete this file? Does it stay deleted, or does it > >> re-appear after a few seconds? If it stays deleted, then the database > >> was not closed but the process was stopped. If it re-appears, then the > >> process is still running. > >> > >> > You are saying: > >> >>>This is a bit strange. Tomcat should dispose the connection pool, > >> >>>which in turn should close all connections to the database. That > would > >> >>>delete the .lock.db file. If it's not deleted, then at least one > >> >>>database connection remains open during the Tomcat shutdown. > >> > >> > But this is the issue of this thread. > >> > >> Well, it's a problem... It might not be your problem. > >> > >> > My application closes all the > >> > connections, which are returned to Tomcat's pool and on shutdown > Tomcat > >> > does > >> > not dispose all of the connections before shutting down the web app > and > >> > so > >> > on and as a result the .lock.db file remains. > >> > >> Well, at the beginning of the mail you wrote you shut down *Tomcat*, > >> not just the web app. If the web app is stopped, then the database > >> stays open, that's correct and OK. > >> > >> > Does your solution solve this issue as well? > >> > >> No. > >> > >> Regards, > >> Thomas > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "H2 Database" group. > > To view this discussion on the web visit > > https://groups.google.com/d/msg/h2-database/-/Xz5bGvt2F-kJ. > > > > 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. > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/QGV_prNUmuYJ. 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.
