Hello! I am trying to encapsulate a system using H2 for testing using non-delegating class loaders, in order to be able to run multiple instances in the same VM. I noticed that the class loaders were not garbage collected, even though they should, and found that H2 was keeping them alive.
I have distilled this problem to a shortish example [1], where a H2 in-memory connection is created and closed under a custom class loader, which is subsequently not released by the garbage collector. If the test()-method invocation is removed, the class loader is garbage collected. I may have missed something, any insight would be helpful. Regards, Erik Karlsson [1] http://pastebin.ca/2022004 -- 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.
