There is a DB_CLOSE_ON_EXIT setting. It in enabled by default, but it can be disabled.
SHUTDOWN command may be executed with other alive connections, they will be closed too, but it's possible that an application will reopen the database after execution of this command, you need to prevent it in some way. Thread.interrupt() may definitely corrupt a database. TCP client threads are not affected, but server threads and threads that use an embedded database should not be interrupted. It's not supported. There is an async filesystem that can be used as a workaround, but it should be carefully tested. Unclean process termination may corrupt the database too in some cases. -- 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.
