[jira] [Comment Edited] (OAK-6479) misleading log entry when there's no revision to write to the journal

["Marcel Reutegger (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OAK-6479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16098058#comment-16098058 ] 

Marcel Reutegger edited comment on OAK-6479 at 7/24/17 8:18 AM:
----------------------------------------------------------------

bq. create a journal entry that already exists

I see, but how is this possible? {{UnsavedModifications.persist()}} will return immediately when there are no pending {{_lastRev}} updates.


was (Author: mreutegg):
bq. create a journal entry that already exists

I see, but how is this possible? {{UnsavedModifications.persist()}} will return immediately when there are not pending {{_lastRev}} updates.

> misleading log entry when there's no revision to write to the journal
> ---------------------------------------------------------------------
>
>                 Key: OAK-6479
>                 URL: https://issues.apache.org/jira/browse/OAK-6479
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: documentmk
>    Affects Versions: 1.0.38, 1.2.26, 1.4.17
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Minor
>              Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4
>         Attachments: OAK-6479.diff
>
>
> When there's no new revision to write to the journal, we see:
> {noformat}
> 21.06.2017 05:04:03.666 *ERROR* [DocumentNodeStore background update thread (1)] org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore Failed to write to journal, accumulating changes for future write (~112 bytes). 
> {noformat}
> This was fixed in 1.6 and newer as part of OAK-3976.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)