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 that you think changes this behavior? If not, why bother? On May 22, 2016 11:26 AM, "Shobhana" <shobh...@quickride.in> wrote: Tim, as you mentioned, I could see one message in many KahaDB log files. I couldn't get JConsole to work with the broker installed on EC2 and Jolokia Rest APIs didn't provide me these stats either. So I just tested by deleting some older KahaDB log files (after taking backup) and restarted the broker by configuring ignoreMissingJournalfiles="true". When the broker started, I could see an INFO message indicating "X" no of messages are dropped from the index where "X" was equal to the no of older files I deleted. So I think each file contained just one message. I'll now test by upgrading to 5.13.3 version. If I upgrade the broker, should I upgrade the jars on my client side as well? Or is it optional? I think I should upgrade. -- View this message in context: http://activemq.2283324.n4.nabble.com/AMQ-5-13-2-Kaha-DB-logs-cleanup-issue-tp4712046p4712250.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
