Gary,
I got 11 files from April 5 (db-9.log - db-19.log), 9 files from April 7
(db-301.log, db-303.log - db-310.log) and one with the current time stamp of
April 12 (db-681.log). Time to live is 2 hours so April 5-7 files are not
expected to be there.
It's now running with debug traces and I'll
To my knowledge 5.5 resolves all know issues with data file cleanup. One
case where seemingly un referenced files remain is where they contain acks
to messages in other data files, so their removal could result in duplicate
delivery on recovery.
There is now detailed trace log messages from the jou
This is something that affects some of my installations.
Is there any reason not to delete a file that should have been removed by now?
James
On 11 April 2011 20:37, BD wrote:
> A bit more info on older kahadb journal files. I checked and they are not
> open by any process. Deleting them frees
A bit more info on older kahadb journal files. I checked and they are not
open by any process. Deleting them frees up disk space.
If I don't need older messages is it ok to delete old kahadb files or will
it cause problems to the broker?
Is there a tool to read these files to find out which messa
Purge and delete the queues (and wait some minutes).
B.D. wrote:
>
> Purging queues using admin console does not get rid of these files
>
--
View this message in context:
http://old.nabble.com/KahaDB-data-files-not-cleaned-up-tp27441942p28746596.html
Sent from the ActiveMQ - User mailing
og then next is
> db-400.log, so big gap)
>
> -Original Message-
> From: B.D. [mailto:boris.dain...@gmail.com]
> Sent: Monday, February 08, 2010 8:39 AM
> To: users@activemq.apache.org
> Subject: Re: KahaDB data files not cleaned up
>
>
> Any suggestions
al Message-
From: B.D. [mailto:boris.dain...@gmail.com]
Sent: Monday, February 08, 2010 8:39 AM
To: users@activemq.apache.org
Subject: Re: KahaDB data files not cleaned up
Any suggestions on how to prevent pileups of data/kahadb/db-xxx.log files?
I just had to clean up 301 data/kahadb/db-xxx.log
Any suggestions on how to prevent pileups of data/kahadb/db-xxx.log files?
I just had to clean up 301 data/kahadb/db-xxx.log files that accumulated on
a QA machine over 6 days. Message time to live is one day so that should not
be happening.
Logs show KahaDB cleanup was taking longer than expe
