Hi, I have a sample of h2 failing when used with spring integration jdbc message channel store that times out on lock. Adding mvcc fixes that particular problem. I will get a minimum test case that demonstrates this. The real issue is by default h2 locks entire table so only one thread can perform dml stuff this makes it unsuitable for our situation. And we actually only use h2 in test we use Oracle or sql server in production On 30/05/2013 5:05 PM, "Noel Grandin" <noelgran...@gmail.com> wrote:
> > On 2013-05-30 08:42, Jason Pell wrote: > >> I find it strange that more attention has not been paid to it is all. >> > Mostly because most of us don't use it, we find the normal mode to be > pretty peachy. > > Now, I have noticed that over the last year various people have bumped > into locking issues, some of which manifest as LOCK TIMEOUT, and we have > fixed various of those. > So might make sense for you to re-examine your workload on H2 (without > using the MVCC mode). > And if you bump into a LOCK TIMEOUT bug there, I'm willing to look into it. > > -- 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 h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
