Hi Tim, I tried 5.13.3 and all further versions till 5.14.0, but this problem is still not gone. I still see a lot of Kaha DB log files which consume huge amounts of disk space and eventually the broker stops functioning!
I made some more changes to check if I could get rid of this problem : a) I enabled following plug-in to set expiry of 1 day for every message (we use only MQTT messages) : <plugins> <discardingDLQBrokerPlugin dropAll="true" dropTemporaryTopics="true" dropTemporaryQueues="true" /> <timeStampingBrokerPlugin ttlCeiling="86400000" zeroExpirationOverride="86400000"/> </plugins> b) I enabled DLQ to drop all expired messages for all topics and queues : <deadLetterStrategy> <sharedDeadLetterStrategy processExpired="false" /> </deadLetterStrategy> <discardingDLQBrokerPlugin dropAll="true" dropTemporaryTopics="true" dropTemporaryQueues="true" /> c) I enabled offline durable subscribers to timeout after 1 day : offlineDurableSubscriberTimeout="86400000" offlineDurableSubscriberTaskSchedule="3600000" After these changes, I could see a few log files got deleted, but majority of the log files remain in the Kahadb folder which consume lot of disk space. I observed this in our production server where I cannot enable trace or JMX. Is there any other way to identify what is causing this issue? TIA, Shobhana -- View this message in context: http://activemq.2283324.n4.nabble.com/AMQ-5-13-2-Kaha-DB-logs-cleanup-issue-tp4712046p4717976.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.