Actually it happens in the context of a long running process where the steps are executed concurrently. Some transactions can span a few minutes, however the inserts are small and fast and happen at the end of each step.
It happens in production only because we process real data. In dev mode the steps are much faster and we don't have this issue (although there are actually more concurrent inserts since the steps take less time to complete). I'm note quite sure it is an issue with H2 after all. I tried to increase the session timeout up to 1 minute but it didn't work. However, if I catch the exception and I retry the insert, the next time it works. I do that during the same transaction, I guess the thrown exception does not mean H2 is in an inconsistent state and I should rollback before retrying? If the retry is ok as far as H2 is concerned, then it would solve my problem and I could keep working with H2 :D -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
