[
https://issues.apache.org/jira/browse/AMQ-7225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864139#comment-16864139
]
ASF subversion and git services commented on AMQ-7225:
------------------------------------------------------
Commit ef0ec42885dc82bb31f266cc6cfe3c4065438453 in activemq's branch
refs/heads/activemq-5.15.x from gtully
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=ef0ec42 ]
AMQ-7225 - defer cleanup task operation till recovery processing complete,
track prepared location in recovered ops to ensure they are retained on
recovery failure. Fix and test
(cherry picked from commit 93e726d6a7ba9ed44f5440369f8f9f1b41f49373)
> [mKahadb] over eager cleanup processing during recovery
> -------------------------------------------------------
>
> Key: AMQ-7225
> URL: https://issues.apache.org/jira/browse/AMQ-7225
> Project: ActiveMQ
> Issue Type: Bug
> Components: Message Store
> Affects Versions: 5.15.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Fix For: 5.16.0
>
>
> it is possible to generated a failed recovery (and failed broker start) with:
> {code:java}
> java.io.IOException: Could not locate data file <..>
> {code} potentially leading to heuristic rollbacks or partially completed
> transactions.
> the cleanup task is kicked off in parallel with recovery which is the root
> cause of the problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
