Hi Thomas, 1) So far I didn't get a memory leak problem e.g. reported by profiler. I only get these log warnings which hint that there is such a problem. At this point anyone reading these logs can only assume that there is a memory leak. 2) I occusionally end up (when shutting down Tomcat) with a "redirectServer.lock.db". I think this is related to the issue we are discussing. This is also a problem for me since my app is part of an rpm installation and on uninstall due to existing redirectServer.lock.db the directories are not cleaned.
>From what you are saying, your approach is to "mask" the warning? You are saying that there is no actually memory issue here? Because in my mind it seems to me that there is a subtle "race-condition" since H2 expects all connections to be closed in order to shutdown properly, but it is Tomcat that decides when to close all the connections. On May 24, 8:27 pm, Thomas Mueller <[email protected]> wrote: > Hi, > > I could reproduce the log message now and I think I found a way to avoid it. > > Just to make sure: you didn't in fact see any out of memory problems, > or similar, right? It's just the message in the log file? > > Regards, > Thomas -- 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.
