checkForCorruptJournalFiles checks to ensure the appropriate kahadb indexes are initialised correctly for each destination on the broker during broker startup. However it does not walk the indexes, to verify that the locationIndex and orderIndex are completely in sync with each other.

In the case where there are still some valid messages on a destination followed by index corruption; this will allow the checkForCorruptJournalFiles to pass without triggering a index file rebuild - which it should in that case.