You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are getting following exception "org.h2.jdbc.JdbcSQLException: Database may be already in use" because of the existence of db.lock.db file.
Observation:
As per our observation, this happens during our service failover; when abrupt killing of JVM happens. While this happens, it is not able to clear H2 DB lock file db.lock.db. This file is created by H2 DB itself internally (org.h2.engine.Database.open(int,int) method is where it opens) as a file lock.
Interestingly H2 DB already provides a JVM shutdown hook registered (see org.h2.engine.Database.openDatabase(int,int,boolean) for details) to clear these artifacts, but unfortunately even this shutdown hook is not able to take care of this lock.
Please let us know your valuable inputs on this ASAP.
Environment Details:
H2 Version: 1.3.169
Thanks,
Krutik
The text was updated successfully, but these errors were encountered:
Hi There,
We are getting following exception "org.h2.jdbc.JdbcSQLException: Database may be already in use" because of the existence of db.lock.db file.
Observation:
As per our observation, this happens during our service failover; when abrupt killing of JVM happens. While this happens, it is not able to clear H2 DB lock file db.lock.db. This file is created by H2 DB itself internally (org.h2.engine.Database.open(int,int) method is where it opens) as a file lock.
Interestingly H2 DB already provides a JVM shutdown hook registered (see org.h2.engine.Database.openDatabase(int,int,boolean) for details) to clear these artifacts, but unfortunately even this shutdown hook is not able to take care of this lock.
Please let us know your valuable inputs on this ASAP.
Environment Details:
H2 Version: 1.3.169
Thanks,
Krutik
The text was updated successfully, but these errors were encountered: