[AMQ-6207] KahaDB: corruption of the index possible on sudden stop of the broker

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.11.4, 5.12.3, 5.13.2
• Fix Version/s: 5.13.3, 5.14.0
• Component/s: KahaDB
• Assignee: Timothy A. Bish
• Reporter: Timothy A. Bish
• Created: 10/Mar/16 23:32
• Updated: 12/Apr/16 21:45
• Resolved: 11/Mar/16 16:14

Description

On a sudden stop of the broker it's possible for the KahaDB index to become corrupt and the broker will refuse to start. The issue is in the PageFile code that is mixing writes to both the recovery file and the index file. The writes need to happen in a deterministic way such that the recovery file isn't missing data that might make it into the the main index file.

Issue Links

• duplicates: AMQ-5440 KahaDB error at startup "Looking for key N but not found in fileMap"