[
https://issues.apache.org/jira/browse/OAK-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440422#comment-13440422
]
Stefan Guggisberg commented on OAK-267:
---------------------------------------
while i still can't explain how a private branch commit could possibly become a
HEAD
i've added code in svn r1376578 that throws an exception should the same error
occur again.
the callstack of that exception should hopefully help investigating the root
cause.
> Repository fails to start with - "cannot branch off a private branch"
> ---------------------------------------------------------------------
>
> Key: OAK-267
> URL: https://issues.apache.org/jira/browse/OAK-267
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: mk
> Affects Versions: 0.5
> Reporter: Chetan Mehrotra
> Priority: Minor
> Attachments: stacktrace.txt
>
>
> On starting a Sling instance I am get following exception (complete
> stacktrace would be attached)
> {noformat}
> org.apache.jackrabbit.mk.api.MicroKernelException: java.lang.Exception:
> cannot branch off a private branch
> at
> org.apache.jackrabbit.mk.core.MicroKernelImpl.branch(MicroKernelImpl.java:508)
> at
> org.apache.jackrabbit.oak.kernel.KernelNodeStoreBranch.<init>(KernelNodeStoreBranch.java:56)
> at
> org.apache.jackrabbit.oak.kernel.KernelNodeStore.branch(KernelNodeStore.java:101)
> at org.apache.jackrabbit.oak.core.RootImpl.refresh(RootImpl.java:160)
> at org.apache.jackrabbit.oak.core.RootImpl.<init>(RootImpl.java:111)
> at
> org.apache.jackrabbit.oak.core.ContentSessionImpl.getCurrentRoot(ContentSessionImpl.java:78)
> at
> org.apache.jackrabbit.oak.jcr.SessionDelegate.<init>(SessionDelegate.java:94)
> at
> org.apache.jackrabbit.oak.jcr.RepositoryImpl.login(RepositoryImpl.java:137)
> {noformat}
> This error does not away after restart also. On debugging
> StoredCommit#branchRootId was not null.
> I think the last shutdown was clean as per the logs. I was debugging some
> query issue which resulted in an exception so that might have something to do
> with this. Logging a bug for now to keep track. If complete repo (~70 MB of
> .mk folder)is required then let me know and I would share it somewhere
--
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