you can read org.apache.activemq.store.kahadb.MessageDatabase#createPageFile to understand how it works
if you remove them yourself the in memory index of kahadb will be broken and then behavior is up to the good will of the process which is rarely in a good mood if you get the idea ;). If you activate the debug logs on org.apache.activemq.store.kahadb.MessageDatabase you should see several messages and a "Checkpoint started." or another "gc candidates after tx range" showing it tries to cleanup *unused* files (completed). Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> 2016-10-06 18:53 GMT+02:00 mean_bcp <[email protected]>: > Actually, please ignore the statement about db.data being 6GB and growing, > I > got some bad information there. > > I am curious about cleaning up the db-xx.log files though, and if I can > configure that automatically. If not, what are the ramifications of > cleaning > them up with a cron job occasionally? > > Thanks > > > > -- > View this message in context: http://tomee-openejb.979440. > n4.nabble.com/KahaDB-growth-tp4680295p4680305.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
