[jira] [Issue Comment Deleted] (AMQ-6207) KahaDB: corruption of the index possible on sudden stop of the broker

["Jeff Genender (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-6207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Genender updated AMQ-6207:
-------------------------------
    Comment: was deleted

(was: This actually looks like its related to AMQ-5695.  Any reason why this wasn't back ported to the aforementioned version branches?  If this truly does fix up those versions, this is a good candidate to be in those other releases.)

> KahaDB: corruption of the index possible on sudden stop of the broker
> ---------------------------------------------------------------------
>
>                 Key: AMQ-6207
>                 URL: https://issues.apache.org/jira/browse/AMQ-6207
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: KahaDB
>    Affects Versions: 5.11.4, 5.12.3, 5.13.2
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 5.14.0, 5.13.3
>
>         Attachments: kahadb-corruption.tar.bz2
>
>
> 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.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)