activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Green <>
Subject Re: KahaDB storage size grows despite almost no pending messages
Date Wed, 08 Jun 2011 08:40:51 GMT
I experienced the same. To debug add the following to your
file (if needed):

log4j.appender.kahadb.layout.ConversionPattern=%d [%-15.15t] %-5p
%-30.30c{1} - %m%n, kahadb

Restart AMQ and let the pruner process run (give it a minute or two for

Examine the log file and look for pruning of the queues. It gives the queue
and the log file numbers that remain candidates for removal.

At some point you'll hit a queue and the number of logs will suddenly drop
unexpectedly. That queue has likely got messages that AMQ is holding a
reference to.

In our case we had NC_ durable clients that had long been disposed of by
ourselves. After deleting these the subsequent expiring / purging run of
kahadb removed the files and freed up literally gigs of space.

Hope this helps. It should really be documented as a FAQ!


On 4 June 2011 19:38, Martin C. <> wrote:

> Hi,
> I experience the problem that over time my KahaDB storage fills up
> despite almost no queue showing pending messages. I upgraded from
> ActiveMQ 5.4.2 to 5.5.0 because I thought that according to the change
> log these leaks in KahaDB should be fixed in 5.5.0, but for me it
> seems they aren't. What can I do to diagnose the problem further?
> I'll try if restarting the broker alone is enough to clean the store,
> but I'll have to wait for our next maintenance interval before I can
> try this.
> Best regards,
> Martin

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message