views:

312

answers:

1

The JBoss developers warn against the use of HSQLDB as a persistent storage (see JBoss wiki). I am confused though, because HSQLDB appears to be used heavily in production.

Especially, the above mentioned page seems to warn against the use of HSQLDB entirely and not against the use in conjunction with JBoss.

Is it still not recommendable to use HSQLDB in JBoss (particularly, the bundled default datasource in Community JBoss 5.1)?

*:We plan to use it in in-memory mode.

+1  A: 

If your own link doesn't convince you, then consider that using it in in-memory mode can lead to undesirable effects when JMS queues get backed up -- JBoss will start trying to persist the messages to the backing store to free heap space, but that won't actually help. Soon, you're spinning in GC or throwing OOM exceptions.

pra
I see the point. But ensuring that the messages are not retried infinitely, giving it enough heap space etc., that risk can basically be removed, right?
Enno Shioji
Maybe... if you're confident that all of the code in your application will be held to the same high standard, even after you're gone and it's being maintained by someone who doesn't know anything about hypersonic and its pitfalls.It seems like you're motivated to keep HSQLDB for some reason; maybe there's another question in there.
pra
Hmmm... I'll give it a good thought one more time. Thanks for the advice!
Enno Shioji