have a read of http://activemq.apache.org/why-do-kahadb-log-files-remain-after-cleanup.html
The logging referenced there will show you what destinations are holding on to references to the journal data files. w.r.t the usage %, the journal size increases in chunks of data file size, so a new journal data file can push the usage over the limit. On 23 October 2012 09:15, Gilles Harloux <gilles.harl...@gmail.com> wrote: > Hi, > > I have a system embedding a broker with KahaDB as a store. I am trying > to get a feel about disaster recovery behavior. So what I am basically > doing is randomly kill & restart the process. I see a condition (after > killing & restarting multiple times) where the messages get consumed, > but kahaDB journal files (db-*.log) don't get reclaimed. As I set up a > storeUsage limit, it ends up blocking the system. > > I say the messages get consumed, because I can see my application > logging what messages it gets to handle; Also, JMX tells me that the > broker's TotalMesageCount is zero, while the StorePercentUsage is > above 100 (depending on parameters such as message size & rate, I saw > anything from 112 to 293 percent usage). > > So, two questions: > - How is it possible (for any reasons) to get a usage percentage > above 100? (In other situations, I saw it happen with memory too). > - Why is it I can't get kahaDB to reclaim seemingly unused journal files? > > TIA, -- http://redhat.com http://blog.garytully.com
