Re: AMQ 5.13.2 : Kaha DB logs cleanup issue

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)

Re: AMQ 5.13.2 : Kaha DB logs cleanup issue

Sorry, my brain's not working. Definitely try 5.13.3 to see if the fix for the bug I referenced and you found (yes, that's the one) allows deletion of the old files. On May 23, 2016 6:54 AM, "Tim Bain" wrote: > We try not to break backwards compatibility between versions,

Re: AMQ 5.13.2 : Kaha DB logs cleanup issue

We try not to break backwards compatibility between versions, but since no one formally tests cross-version compatibility, it's not guaranteed. But between 5.13.2 and 5.13.3, we should not have knowingly made a breaking change. Why are you trying 5.13.3? Is there a bug in the release notes

Re: AMQ 5.13.2 : Kaha DB logs cleanup issue

When checked using the Jolokia Rest APIs, I get same result ... enqueued message count on these topics show 0; so I guess the Jolokia Rest APIs also give only stats since the broker started last. -- View this message in context:

Re: AMQ 5.13.2 : Kaha DB logs cleanup issue

Sure, I'll check when I have some time. Btw, I tried to use JConsole to view the current status of consumers. I tried hard getting JConsole to connect to my broker that runs on an EC2 instance, but couldn't succeed. Can I use the Jolokia Rest APIs instead? Do these APIs give same result as JMX

Re: AMQ 5.13.2 : Kaha DB logs cleanup issue

You're right, your interpretation is consistent with the documented example, whereas mine is consistent with the text of the log line. In that situation, I always assume the documentation is wrong, but that's just an assumption. If you or someone else has time to look at the algorithm and

Re: AMQ 5.13.2 : Kaha DB logs cleanup issue

Thanks Tim, I did not know that the stats are reset when the broker is restarted. I'll check how to use JConsole to view the current status of consumers. Yes, all topics have durable subscribers. I used the logic mentioned in the example given at

Re: AMQ 5.13.2 : Kaha DB logs cleanup issue

As far as I know, the stats cover only the time since the broker was last restarted, so seeing zeros is no guarantee that there are no pending messages in the persistence store. I would use a JMX viewer such as JConsole to look at what the broker thinks is the current status of the consumer(s) on

AMQ 5.13.2 : Kaha DB logs cleanup issue

We use AMQ to exchange MQTT messages. I observed that the log files in Kaha DB don't get deleted even after many days. I used the steps mentioned in http://activemq.apache.org/why-do-kahadb-log-files-remain-after-cleanup.html