[
https://issues.apache.org/jira/browse/AMQ-6815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16322176#comment-16322176
]
Christopher L. Shannon commented on AMQ-6815:
---------------------------------------------
[~gtully] - thanks for fixing this memory leak...I actually saw an OOM error
because of this a couple weeks ago before vacation but I didn't get a chance to
get back to investigating it yet.
> 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)
