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-3180) Versioning: improve diagnostics when version history state is broken
Date Wed, 05 Aug 2015 13:18:04 GMT

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

Julian Reschke commented on OAK-3180:
-------------------------------------

Thanks for checking. My patch is based on 1.0 which doesn't have getExistingBaseVersion, so
it's not needed here. The better solution then is to backport this change.

> Versioning: improve diagnostics when version history state is broken
> --------------------------------------------------------------------
>
>                 Key: OAK-3180
>                 URL: https://issues.apache.org/jira/browse/OAK-3180
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.2.3, 1.3.3, 1.0.18
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>             Fix For: 1.2.4, 1.0.19
>
>         Attachments: OAK-3180.diff
>
>
> Users suffering from the problem described in OAK-3169 may encounter NPEs upon checkin(),
as ReadWriteVersionManager.checkin() does not check the return value of getExistingBaseVersion()
for null. Even if we can't fix the underlying problem easily, we should at least provide better
diagnostics.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message