I no longer think that it is a multithreading table lock order problem. In such a case H2 threw a JDBCException and rolled back all related transactions.
In my case the transactions are not rolled back but the H2 code created a deadlock as it can be seen from the stack traces. So the problem seems to be H2 internal. Uli -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
