Unfortunately we currently have another case of database corruption. The exception stack trace is identical to the one I posted above. What strikes me is that the messages reads "database: flush" and subsequently the stack trace seems to imply the database is being opened. That sounds contradictory to me.
The only common denominator is that all databases are MVStore ones. Connections are not shared among threads but multiple threads do access the same database via separate connections at the same time. Could something be off there? We do exactly the same thing with the PageStore databases we have left in operations but none of these have gone bad during these last weeks running on 199. I am considering reverting to version 196. Is that even an option after databases have been written (and possibly even created) using 199? -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/5af4c8a8-0de5-4ac1-bc82-819dc5f63f39%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
