[
https://issues.apache.org/jira/browse/OAK-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979456#comment-13979456
]
Thomas Mueller commented on OAK-1751:
-------------------------------------
With the test case (but without applying the rest of the patch), I can not
consistently reproduce the issue, even if I change from MicroKernelException to
IllegalStateException, and even if I use more threads and a longer loop. But
setting a breakpoint at the exception works. I will try to change the test case
to better report the problem.
> DocumentNodeStore may detect conflict too late
> ----------------------------------------------
>
> Key: OAK-1751
> URL: https://issues.apache.org/jira/browse/OAK-1751
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, mongomk
> Affects Versions: 0.20
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Critical
> Fix For: 1.1
>
>
> Under load and with concurrent commits to the same node it may happen that
> the DocumentNodeStore detects a conflict too late and throws an exception
> like this:
> {noformat}
> MicroKernelException: Unable to annotate our revision with collision marker.
> Our revision: r1458568cc53-0-1, ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
