Are you saying that you are running hsql as JMS store in production? In any case, JBoss recommends replacement of HSQL with a 3rd party stable database for production.
We have included hsql as a small footprint database for testing purposes only. You should migrate to a different database. Look under docs/examples/jca for datasource config files for various databases.
2 gigs isn't very large, especially for a database. You can move it to a different disk.
You can issue CHECKPOINT DEFRAG safely during server operation, though it stops the whole JMS server.
I would suggest upgrading to HSQL 1.7.2.
Because of performance issues I need that the jms storage will be local on the same server the jboss run and not on remote database.
Can I do it with the hsql database or file-pm-service.xml ? or the jboss doesn't support local jms persistent ?
How can I issue CHECKPOINT DEFRAG ?
Get a javax.sql.DatasSource via JNDI, I guess "java:/localDB". Then get a connection, issue "CHECKPOINT DEFRAG", close the connection, etc. HSQL also issues this command after ever 200MB is inserted. This won't damage your data, but as I said will cause JMS to block.
Again, try to upgrade to 1.7.2 which will be part of 3.2.6. (Rember to back-up your data.)
Also, if you're still having trouble you can also get help from http://sf.net in the HSQL forum.
It works fine.
we are having the same problem. We are using JBoss 4.03.
I would like to configure SET CHECKPOINT DEFRAG <VALUE>
in combination with the SET LOGSIZE <VALUE>
instead of manually triggering it.
Does anyone know how to configure it in JBoss? Can I put it
somewhere in the hsql-ds.xml file -> I found a mbean there
which has <attribute> tags nested. Is this the right place?
I have not found any documentation about that.
I hope anyone can help
Thanks & regards