Yes, databases are shutdown and reopened constantly since the connection pool will only keep unused connections around for a short period of time before closing them. As a result databases are closed by H2 automatically once the last connection is closed. This particular type of issue appears to result in database corruptions that usually do not show up until the database is closed and reopened.
I realize that changes are necessary and appreciate the performance improvements which are more than noticeable. I am merely trying to find out if some things may have changed that make my usage pattern (accessing many embedded databases from the same process with a connection pool that opens/closes connections at a quite high rate) possibly more fragile. If so, I would be more than willing to make adjustments or do specific testing. As a software developer I understand how hard it can be to find issues when they can not be reproduced predictably. The problem occurs intermittently so might be related to specific timing or synchronization scenarios. -- 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/4c45cd76-2291-48c6-a3a4-026bc9ce9f6a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
