I agree, I don't see anything obvious in that log. You could try checking the H2 .trace.log file which lives next to the DB file, sometimes that manages to capture exceptions that the application ignores.
interrupt() closes the NIO FileChannel object, which means the whole DB is effectively shutdown. The data is fine, but you'd need to reconnect to the DB. To work around this, you could try running the DB in TCP server mode. Then interrupt() will just close the java.sql.Connection object that that Thread is using, instead of shutting down the DB. -- 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 h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
