Installing a simple Grails application in Tomcat on Linux should really have been the most straightforward of tasks. Instead, I spent a progressively more frustrating morning chasing down a "helpful" feature of HSQLDB that was causing the startup to fail with
org.hsqldb.HsqlException: The database is already in use by another process:
org.hsqldb.persist.NIOLockFile@6b67bdbe[file =/myDb.lck, exists=true, locked=false, valid=false,
fl=null]
exceptions. To save others from a similar waste of time, here’s the cause and a workaround:
Cause
Between versions 1.7.2. and 1.8.0.10., HSQLDB attempts to lock the files for file-based DBs in order to "[protect] the user from running the process twice with the same files and corrupting his data", apparently. Unfortunately, if your DB files reside on NFS, which doesn’t support these locks, HSQLDB will blow up with the above exception.
It seems that there have been enough problems with this that HSQLDB has reverted to not using locks by default in 1.8.0.10., although this may be changed again in future versions, it seems.
Workaround(s)
- Move your DB files to a non-NFS location
- Upgrade to version 1.8.0.10. (or a pre-1.7.2. version)
- Use a mem rather than a file DB
The details are described in this thread from the HSQLDB forums.
From what is mentioned there, it would seem to be possible to disable file locking somehow. I tried hsqldb.nio_data_file=false, but that doesn’t seem to do the trick. If anyone finds out how to do this please add a comment!
Bug
Resolved
Major
The original exception should be forwarded to be printed with the error message.
After to have added stacktrace print into the source code, the root cause is:
A Google's search result is: http://blog.xebia.com/2009/03/hsqldb-database-already-in-use-by-another-process-exceptions-on-linux
Installing a simple Grails application in Tomcat on Linux should really have been the most straightforward of tasks. Instead, I spent a progressively more frustrating morning chasing down a "helpful" feature of HSQLDB that was causing the startup to fail with
org.hsqldb.HsqlException: The database is already in use by another process:
org.hsqldb.persist.NIOLockFile@6b67bdbe[file =/myDb.lck, exists=true, locked=false, valid=false,
fl=null]
exceptions. To save others from a similar waste of time, here’s the cause and a workaround:
Cause
Between versions 1.7.2. and 1.8.0.10., HSQLDB attempts to lock the files for file-based DBs in order to "[protect] the user from running the process twice with the same files and corrupting his data", apparently. Unfortunately, if your DB files reside on NFS, which doesn’t support these locks, HSQLDB will blow up with the above exception.
It seems that there have been enough problems with this that HSQLDB has reverted to not using locks by default in 1.8.0.10., although this may be changed again in future versions, it seems.
Workaround(s)
The details are described in this thread from the HSQLDB forums.
From what is mentioned there, it would seem to be possible to disable file locking somehow. I tried hsqldb.nio_data_file=false, but that doesn’t seem to do the trick. If anyone finds out how to do this please add a comment!
- Move your DB files to a non-NFS location
- Upgrade to version 1.8.0.10. (or a pre-1.7.2. version)
- Use a mem rather than a file DB
The details are described in this thread from the HSQLDB forums. From what is mentioned there, it would seem to be possible to disable file locking somehow. I tried hsqldb.nio_data_file=false, but that doesn’t seem to do the trick. If anyone finds out how to do this please add a comment!