Hi, Please note it's not the *size* of an uncommitted transaction that is a problem. The problem is, once you have an uncommitted transaction (which could mean there is only one row changed in the uncommitted transaction), then the transaction log is not truncated starting from that point on. So the *starting* time of the uncommitted transaction is the problem.
To get more details about transactions, you could run the Recover tool with the "-transactionLog" option. This option is not yet documented, because I thought it is not useful in general. But I will document it now. Regards, Thomas On Mon, Aug 19, 2013 at 7:44 PM, Noel Grandin <[email protected]> wrote: > This looks to me like you have code that is allocating connections > from a pool, making some changes, not committing those changes, and > not bothering to close the connection. > > -- > 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. > -- 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.
