You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (Updated) (JIRA)" <ji...@apache.org> on 2011/11/08 13:54:51 UTC
[jira] [Updated] (JCR-3017) Version history recovery fails in case
a version does not have a jcr:frozenNode
[ https://issues.apache.org/jira/browse/JCR-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-3017:
-------------------------------
Issue Type: Bug (was: Improvement)
> Version history recovery fails in case a version does not have a jcr:frozenNode
> -------------------------------------------------------------------------------
>
> Key: JCR-3017
> URL: https://issues.apache.org/jira/browse/JCR-3017
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: versioning
> Reporter: Honwai Wong
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 2.2.10, 2.3.1
>
> Attachments: JCR-3017.patch
>
>
> With JCR-2551 in place, a version recovery mode has been introduced. Problem now is that in case a version is encountered that misses a mandatory jcr:frozenNode, an InternalError is thrown by o.a.j.c.version.InternalVersionHistoryImpl#createVersionInstance. Since o.a.j.c.RepositoryChecker#checkVersionHistory only catches Exception, it fails to catch it properly which leads to a complete repository shutdown.
> Throwing for example a RuntimeException instead fixes the problem.
--
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