Hypersonic File Size

[wikey]

Hi,

I'm using JBOSS 4.0.0 and having problem with the uncontrol hypersonic file size.

It keeps growing even the messages already cleared from the JMS_MESSAGES table where the durable subriber already received the file and clear from the table.

For each 200,000 messages process. It grows 64MB and also i having problem restart the JBOSS till i replace the localDB.data file with the original file.

How do i control this?

[genman]

Download HSQLDB 1.8 from the web site and replace the current hsqldb.jar file with it. JBoss 3.2.7 might also be shipping with this versoin.

[wikey]

Hi,

Still the same after the upgrade...the file size still growing till i restart my JBOSS
Anything else i can do?

below is the properties file created once i start tomcat.
#HSQL Database Engine
#Fri Apr 29 18:15:43 SGT 2005
hsqldb.cache_file_scale=1
runtime.gc_interval=0
hsqldb.first_identity=0
version=1.8.0
modified=no
hsqldb.script_format=0
sql.enforce_size=false
hsqldb.cache_size_scale=8
hsqldb.cache_scale=14
hsqldb.log_size=200
sql.enforce_strict_size=false
readonly=false
hsqldb.compatible_version=1.7.2
hsqldb.original_version=1.8.0
sql.compare_in_locale=false
hsqldb.nio_data_file=true
hsqldb.cache_version=1.7.0
hsqldb.default_table_type=memory

[darranl]

You should look at using a different database other than Hypersonic.

http://www.jboss.org/wiki/Wiki.jsp?page=ConfigJBossMQDB

[wikey]

i'm trying with the mysql but it's 3-4 times slower, anyway to fine tune it...index oredi set to the TXID and TXOP field from JMS_Messages table

[genman]

For 1.8, the file size will continue to grow until a certain point and then will be compacted automatically. You should not "run out" of space, although it may seem like it grows without bound.

[jeffdo666]

I'm still experiencing this problem using JBoss 4.0.5 with the latest version of Hypersonic (1.8.0.7). My localDB.data is still growing out of control despite all the documentation that says otherwise.

[genman]

If you have an issue with it, bring it up with the HSQL team.

It's not unusual to have it be > 1GB at times.