What does one of your database URLs look like?
Are you perhaps call Thread.interrupt somewhere?
If so, that would close the database abruptly and force it to be re-opened on
the next connection attempt.
Doing that enough times is likely to cause corruption, because all kinds of stuff could be in-flight and unwritten to
actual physical storage.
That is currently our weak link - we are not sufficiently tolerant of systems with large write queues that re-order
stuff before it hits disk.
--
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/a8233643-1ed0-d94c-b0bc-cfdc00e9cc5e%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
