MVCC is still experimental. It works fine for some people, but others see corruption.
So I would suggest that you drop the use of MVCC and fix the deadlocks - the error message is normally pretty informative, and re-ordering some of your queries and using FOR UPDATE elsewhere normally solves the deadlock issue.
On 2014-03-21 11:42, Frédéric Gendebien wrote:
For a personal project I am using H2 database (1.3.175) with Datanucleus JPA (3.2) provider and I faced systematically file corruption when I reboot my server. I cannot use server mode because my server is an embedded device with very low resources so I am using file mode with MVCC=TRUE. My application is multi-threaded so without MVCC I faced dead locks...
-- 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/d/optout.
