You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2016/05/03 13:49:12 UTC

[jira] [Resolved] (AMQ-6277) KahaDB does journal recovery for last append in error in normal restart case

     [ https://issues.apache.org/jira/browse/AMQ-6277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-6277.
-----------------------------
    Resolution: Fixed

> 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)