[
https://issues.apache.org/jira/browse/AMQ-6207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15191084#comment-15191084
]
ASF subversion and git services commented on AMQ-6207:
------------------------------------------------------
Commit 3dc769d1f66e50c96dec6d634e1a347a577e7725 in activemq's branch
refs/heads/activemq-5.13.x from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=3dc769d ]
https://issues.apache.org/jira/browse/AMQ-6207
Perform writes / sync in predicatable order first to the recovery file
and then into the main index file.
(cherry picked from commit b39ab7867c208a967090eff189594c2b06dafb34)
> 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)
