jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-6479) misleading log entry when there's no revision to write to the journal
Date Wed, 10 Jul 2019 12:57:00 GMT

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

Julian Reschke commented on OAK-6479:
-------------------------------------

So this is about code that changed between 1.4 and 1.6, and what we have in 1.6 and newer
can not easily be backported.

Proposal: close as "won't do".

> 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
>            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
(v7.6.3#76005)

Mime
View raw message