We finally got sick of this issue and migrated to HSQLDB for MVCC and no more missing lob issues. We still use H2, but only for storing configuration stuff that does not need to be updated concurrently. It's a shame more attention has not been shown to this issue, because it was certainly frustrating having to change over to HSQLDB.
On Friday, June 15, 2012 6:08:53 PM UTC+10, Noel Grandin wrote: > > > > On 2012-06-15 09:54, Eoin Byrne wrote: > > It looks like we will have to turn MVCC back on because we are now > > hitting a large number of table lock timeouts but thats going to > > reintroduce the DB file growth issue. I know this feature is > > experimental but I guess my question is how experimental is it? > It works fine for some people, but others experience problems. The > bottom line is that we're just not sure. The people having problems have > never been able to produce us a decent test case, so it's kind of hard > to fix. > > > and assuming the growth is down to long lived connections - is there > > any way to find out what selects / updates are still pending commits > > from the DB logs? > > > Your current best bet is to instrument the H2 code yourself. > I suggest these methods > org.h2.engine.Session#commit() > org.h2.engine.Session#begin() > And then you should be able to track the problem sessions down. > > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
