That make me think that - just in case there were a common cause - we could obtain some useful data even debugging the test case with a breakpoint at the line that would produce the transaction log warning and generating a heap dump at that time. Maybe that could highlight unwanted transaction log related object instances that are somewhat kept referenced and hence not GCed.
2013/8/24 Noel Grandin <[email protected]> > On Sat, Aug 24, 2013 at 4:53 PM, <[email protected]> wrote: > > I don't know if it is related to your problem but I have a memory problem > > with transactions too. > > Weird. I run my stuff for weeks at a time with no problem. > > But we can find out easily - add this option > -XX:+HeapDumpOnOutOfMemoryError to your java startup options. > Let it trigger a heap dump, and then run it through a heap dump > analysis tool like the one in Netbeans or the one in VisualVM. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "H2 Database" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/h2-database/i2fVBYBF3as/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/h2-database. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
