I read a wike page. It said the following  fault of HSQL:

Known problems with Hypersonic Database are:
* No transaction isolation
* Thread and socket leaks - connection.close() does not tidy up resources
* Persistence quality - the database is held in a file in the JBoss data 
directory, it is a
common problem that log becomes corrupted after a failure, leaving you to 
manually
edit the file to recover the database.
* Database Corruption has been reported in many instances
* Stability under load - strange problems have been seen under load, including 
the
database process "vanishing", i.e. it stops processing when too much data is 
sent,
usually because of an OutOfMemory problem, but not necessarily.
* HSQLdb uses a file on the local server - although this can be changed to use a
remote hsqldb instance, this negates many of the benefits of using hsqldb. The 
local
file makes it impossible to use in a clustered environment



Thread and socket leaks - connection.close() does not tidy up resources. Now we 
have the above exception. Is it a bug of HSQLDB?


View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217364#4217364

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217364
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to