[
https://issues.apache.org/jira/browse/AMQ-6277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268571#comment-15268571
]
ASF subversion and git services commented on AMQ-6277:
------------------------------------------------------
Commit ba77b9f55a627846ecab63916b2667f234022d34 in activemq's branch
refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=ba77b9f ]
https://issues.apache.org/jira/browse/AMQ-6277 - tidy up logic that determines
recovery location so that we don't recovery from the end of the journal in
error on normal restart. This avoids suprious recovery logging
> KahaDB does journal recovery for last append in error in normal restart case
> ----------------------------------------------------------------------------
>
> Key: AMQ-6277
> URL: https://issues.apache.org/jira/browse/AMQ-6277
> Project: ActiveMQ
> Issue Type: Improvement
> Components: KahaDB, Message Store
> Affects Versions: 5.13.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Minor
> Fix For: 5.14.0
>
>
> On a normal restart - the journal is replayed from the last append location
> in error. Reporting some unnecessary info logging of the form{code}INFO |
> Recovering from the journal @1:503
> INFO | Recovery replayed 1 operations from the journal in 0.0 seconds.{code}
> Recovery is only required when the last append location is different from the
> recovery location.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
