[
https://issues.apache.org/jira/browse/AMQ-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048612#comment-15048612
]
ASF subversion and git services commented on AMQ-6083:
------------------------------------------------------
Commit 5db5f3e39a682640b64bc904f30cbd2e0e3de4da in activemq's branch
refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=5db5f3e ]
https://issues.apache.org/jira/browse/AMQ-6083 - ignoreMissingJournalfiles
false - check for missing acks and corruption anywhere and error out so that
corruption does not go unnoticed - fix and test
> Broker starts on corrupted kahadb despite checkForCorruptJournalFiles="true"
> and ignoreMissingJournalfiles="false"
> ------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-6083
> URL: https://issues.apache.org/jira/browse/AMQ-6083
> Project: ActiveMQ
> Issue Type: Bug
> Components: KahaDB
> Affects Versions: 5.13.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.14.0
>
>
> Kahadb checkForCorruptJournaFiles will pick up journal corruption via the
> checksum, but if the corrupt locations are not referenced by the index the
> corruption is ignored, even if ignoreMissingJournalFiles (which should be
> called ignoreMissingJournalFilesOrCorruptJournalLocations) is false (the
> default).
> this means that acks can be missing and in the event of a journal replay,
> there is no indication of the missing acks.
> If ignoreMissingJournalFiles=false and corruption or missing journal files
> that just have acks are detected, the broker should error out.
> This ensures that corruption does not go unnoticed and the root cause can be
> determined before restart.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
