Here is a way to determine what is keeping each file in place: * Set the org.apache.activemq.store.kahadb log level to TRACE in the log4j configuration file * Restart the broker * Search the log file for "gc candidate" or "GC Candidate"
The logging generated should explain why each file cannot be removed. Don't forget to turn off the TRACE logging when done! -- View this message in context: http://activemq.2283324.n4.nabble.com/jira-Commented-AMQ-5134-scheduler-db-x-log-can-not-delele-tp4680134p4680135.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
