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 journal that describes the
cleanup process wrt destinations.
On 11 Apr 2011 20:46, "James Green" <james.mk.gr...@gmail.com> wrote:
> 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 <boris.dain...@gmail.com> wrote:
>> 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 message(s) prevent
it
>> from being cleaned up?
>>
>> Thank you
>>
>>
>>
>> --
>> View this message in context:
http://activemq.2283324.n4.nabble.com/KahaDB-data-files-not-cleaned-up-tp3429145p3442915.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
