Using HSQLDB in production environments

Question

I want to use HSQLDB in a production environment to store some data in memory and to export data using files. Does anyone have experience using hsqldb in production environments? Is hsqldb handling server resources gracefully and does it clean up unused resources correctly?

I saw a critical note on these issues from the red hat, and I wonder if this remains for hsqldb:

http://kbase.redhat.com/faq/docs/DOC-15194

Answer 1

I do not know about HSQLDB, but we used H2 for the same purpose without any problems.

Answer 2

I used hsql in many cases in production (mainly as a repository with fast file storage for complex settings) and never encountered any problems.

Answer 3

I can confirm some of the problems listed on the Red Hat page.

We had problems using HSQLDB as a separate instance in the Tomcat container. The application will not close normally and hang on a 100% processor. However, there was a code fix.

We also had problems with some data loss after the server was forcibly killed. I could not reliably reproduce the situation.

I also have the oddity that I cannot run multiple instances of the same application using HSQLDB at the same time.

You need to evaluate whether a standalone, embedded database is the right choice. If integrity and integrity are important, HSQLDB may not be the best choice.

Answer 4

We experienced a database corruption (the entire database was lost) several times a year using HSQLDB when it was not closed cleanly.