[
https://issues.apache.org/jira/browse/AMQ-6815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16171945#comment-16171945
]
ASF subversion and git services commented on AMQ-6815:
------------------------------------------------------
Commit b5f7c15b2518334d338f9fad54696f62ba4c268b in activemq's branch
refs/heads/activemq-5.15.x from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=b5f7c15 ]
[AMQ-6815] have checkpoint validate status of async writes to avoid stale
metadata and validate location size on read to avoid potential oom on restart
(cherry picked from commit 8c3ef6cadb46d9694c68aa649a7952eb1612279f)
> KahaDB checkpoint needs to fail fast in the event of journal write failure
> --------------------------------------------------------------------------
>
> Key: AMQ-6815
> URL: https://issues.apache.org/jira/browse/AMQ-6815
> Project: ActiveMQ
> Issue Type: Bug
> Components: KahaDB
> Affects Versions: 5.15.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.16.0
>
>
> KahaDB checkpoint does some async updated to the journal and syncs to the
> index. However the async journal updates can error out and not get reported
> leading to the index metadata being stale. This can lead to reading an
> invalid location on restart which may result in full recovery of the index.
> Any exception from the async store needs to cause the checkpoint to fail.
> In addition, on reading a corrupt location, we can do a sanity check to avoid
> a potential OOM by validating the size before allocation.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
