I am running some testing and discovered that our KahaDB (which the default configuration was left alone from the ServiceMix install) has log files growing unbounded: ... db-1099.log db-507.log db-627.log db-747.log db-867.log db-987.log db-1100.log db-508.log db-628.log db-748.log db-868.log db-988.log db-1101.log db-509.log db-629.log db-749.log db-869.log db-989.log ... The configuration defaults according to http://activemq.apache.org/kahadb.html Will allow the files to grow up to 32 mb each and has a cleanup running every 30000. However, the log files are in the thousands and continue to grow. Each of these files is 33 MB.
What is the configuration change needed to force KahaDB to clean up the log files? According to the defaults, it looks like this should already be happening. What am I doing wrong? Thanks, Zach Calvert
