[
https://issues.apache.org/jira/browse/JCR-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122806#comment-13122806
]
Jukka Zitting commented on JCR-3101:
------------------------------------
Looks good. As you mentioned, a more fine-grained recovery would be nice, but
for now simply disconnecting a node from a broken version history seems good
enough. Another potentially useful future improvement would be to check not
just the root version but also all other versions in the history.
> recovery tool does not recover when version history can be instantiated, but
> root version can not
> -------------------------------------------------------------------------------------------------
>
> Key: JCR-3101
> URL: https://issues.apache.org/jira/browse/JCR-3101
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Attachments: JCR-3101.patch
>
>
> JCR-2551 introduced a recovery mode which tries to instantiate the version
> history, and if this fails, disconnects the VH (version history) and makes
> the node unversioned.
> However, it appears it can happen that the persistence is damaged such as
> getting the VH does indeed work, but subsequent operations fail due to other
> problems. One problem that has been seen is a missing frozenNode property of
> the root version (or a missing frozenNode itself).
> As a quick fix, we may want to change the checker so that it actually also
> tries to get the rootVersion and it's frozenNode. Long term, depending on how
> frequent this problem is, we may have to think about a less drastic recovery
> than disconnecting the VH.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
