You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2016/05/11 07:05:12 UTC

[jira] [Updated] (OAK-4321) Improve conflict exception message to show if conflict is unexpected

     [ https://issues.apache.org/jira/browse/OAK-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger updated OAK-4321:
----------------------------------
           Labels:   (was: candidate_oak_1_0 candidate_oak_1_2 candidate_oak_1_4)
    Fix Version/s: 1.4.3
                   1.2.15
                   1.0.31

Merged into 1.4 branch: http://svn.apache.org/r1743184
Merged into 1.2 branch: http://svn.apache.org/r1743309
Merged into 1.0 branch: http://svn.apache.org/r1743320

> Improve conflict exception message to show if conflict is unexpected
> --------------------------------------------------------------------
>
>                 Key: OAK-4321
>                 URL: https://issues.apache.org/jira/browse/OAK-4321
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, documentmk
>            Reporter: Vikas Saurabh
>            Assignee: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.6, 1.5.2, 1.0.31, 1.2.15, 1.4.3
>
>         Attachments: OAK-4321-1.0.diff
>
>
> Merge exception (aka OakMergeXXXX) are often expected when concurrent sessions do conflicting writes. But in some occasions, we've seen bugs in oak which also lead to merge exception.
> This creates confusion during investigation to isolate if it's an issue in oak or a genuine concurrent conflict.
> It'd be useful if the exception message has information to distinguish that.



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