Re: Memory Leak in org.apache.derby.impl.io.vfmem.DataStore

Thank you so much... the drop did the trick. On Thu, Mar 16, 2023 at 2:49 PM Stanimir Stamenkov via derby-user wrote: > > Thu, 16 Mar 2023 20:06:09 +0200, /Stanimir Stamenkov/: > > > I'm not finding destroy=true attribute but a drop=true one: > > > >* Setting attributes for the database

Re: Memory Leak in org.apache.derby.impl.io.vfmem.DataStore

Thu, 16 Mar 2023 20:06:09 +0200, /Stanimir Stamenkov/: I'm not finding destroy=true attribute but a drop=true one:   * Setting attributes for the database connection URL (Derby Reference Manual) that is specific for

Memory Leak in org.apache.derby.impl.io.vfmem.DataStore

I work in ActiveMQ Artemis, and we have a series of tests that will use derby memory, with the uri as "jdbc:derby:memory:testName;create=true" So, every test will have its own database, and we do that for isolating the tests. at the end of the test, we call destroy and shutdown of derby with:

Re: Memory Leak in org.apache.derby.impl.io.vfmem.DataStore

Thu, 16 Mar 2023 11:29:10 -0400, /Clebert Suconic/: at the end of the test, we call destroy and shutdown of derby with: try { DriverManager.getConnection("jdbc:derby:memory:test;destroy=true"); } catch (Exception ignored) { // it always throws an exception on shutdown