ok, then it is more for activemq than tomee but cleanupInterval does that job so check with your app what is happening maybe
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:43 GMT+02:00 mean_bcp <[email protected]>: > Thank you. > > What I'm looking for is some advice for limiting the size of the files. I > am > not sure which options can be used, and what the ramifications are. > Currently my db.data is 6GB and growing - does this mean we are not > processing the messages fast enough, or we are saving them too long, etc. I > am not sure how to interpret or fix this issue. If anyone has experience > with this, I would appreciate a nudge in the right direction. > > Also, what is the purpose of the db-xx.log files (I'm assuming some sort of > restore?) and the ramifications of deleting them as a part of an automated > cleanup script? Or can I tweak the kahaDB config to remove them for me? > > > > -- > View this message in context: http://tomee-openejb.979440. > n4.nabble.com/KahaDB-growth-tp4680295p4680303.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
