You might see if you can get debugging output similar to what KahaDB offers:
http://activemq.apache.org/why-do-kahadb-log-files-remain-after-cleanup.html I had a similar situation and the KahaDB debugging showed that the problem was due to un-acked persistent messages sprinkled throughout the older data files, effectively forcing them to stay open and uncollected (one un-acked message in a file that might have dozens or hundreds of siblings was enough to force KahaDB to keep the file around). Jim On Thu, Apr 14, 2016 at 6:07 AM AlexanderMQ <alex.mq2...@gmail.com> wrote: > Hi, > > I have a fairly simple production installation running consisting of > ActiveMQ 5.11.1 using levelDB. Everything configuration is kept like out of > the box, only storeUsage limit is set to 20GB. > > Since a while I see storage leak, every day the reported store percentage > used is raising by 4%, while number of messages in all queues is very low > (<1000) and their size is 2k in average, topics are not used. > > A simple restart of ActiveMQ fixes the problem. > > ActiveMQ log shows only compacting leveldb index every 10s. I'm using a JDK > 1.8u51 32 Bit. > > What is the best approach to tackle this? > > Alex > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Storage-Leak-How-to-analyse-tp4710765.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
