activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Sherman (JIRA)" <>
Subject [jira] [Created] (AMQ-4236) KahaDB Log File Clean Up Using MessageDatabase Trace Logging
Date Fri, 21 Dec 2012 15:43:13 GMT
Jason Sherman created AMQ-4236:

             Summary: KahaDB Log File Clean Up Using MessageDatabase Trace Logging
                 Key: AMQ-4236
             Project: ActiveMQ
          Issue Type: Bug
          Components: Documentation
    Affects Versions: 5.7.0
            Reporter: Jason Sherman
            Priority: Minor

The documentation on the kahaDB log file cleanup located here [1] has a bug.


The information provided about the output is incorrect describing the following two lines:

TRACE | gc candidates after dest:0:D, [86, 87, 163] |
| ActiveMQ Journal Checkpoint Worker
 TRACE | gc candidates after dest:0:E, [86, 87] |
| ActiveMQ Journal Checkpoint Worker

This output indicates that dest:0:E has references to db-163.log and not dest:0:D as the current
information states.

It might be helpful to explain the output a little bit clearly indicating the list of log
files shown is what is available AFTER checking the the destination, as the log output states.
 It just might be helpful to clearly point this out.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message