Using HSQLDB in production environments

Question

I want to use HSQLDB in a production environment for stroring some data in memory and for data export using files. Does anybody have experience with using hsqldb in production environments? Is hsqldb treating server resources gracefully and does it cleanup unused resources properly?

I've seen a critical post on those issues from red hat and I'm wondering whether this still holds for hsqldb:

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

Answer 1

我在生产中多次使用hsql（主要是作为复杂首选项的快速文件存储）并且从未遇到任何问题。

Answer 2

不知道HSQLDB，但我们一直在使用H2而没有任何问题。

Answer 3

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

We have had issues using HSQLDB as a standalone instance in a Tomcat container. The application would not shutdown properly and hang at 100% cpu. There was a code fix, though.

We have also had issues were some data was lost after the server was forcibly killed. I could not reliably reproduce the situations.

I also have some strangeness that I cannot start multiple instances of the same application using HSQLDB at the same time.

You need to evaluate the if a standalone, in-memory DB is the right choice. If consistency and integrity is essential, HSQLDB may not be the right choice.

Answer 4

我们在一年内使用HSQLDB经历了几次数据库损坏（整个数据库丢失），当它没有完全关闭时。