Note that the db-#.log files are not general-purpose error logging files, they are the KahaDB data files.
If KahaDB is holding onto a large number of files, there's a good chance there are old messages around. The first thing to check is that ActiveMQ is not being used as a message store. Old messages can and do lead to large amount of disk space being held. Note that there is no defragmentation of the files, so a single message can hold an entire data file, and due to the need to maintain acks in order to avoid duplicate message delivery after a restart, a single message can lead to holding a long chain of data files. -- View this message in context: http://activemq.2283324.n4.nabble.com/AWS-disk-hosting-ActiveMQ-is-full-UI-purge-delete-doesn-t-work-tp4703991p4704238.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
