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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2017/03/27 05:38:41 UTC

[jira] [Updated] (OAK-3552) Clustering deployment gets a CommitFailedException

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

Chetan Mehrotra updated OAK-3552:
---------------------------------
    Component/s:     (was: core)
                 documentmk

> Clustering deployment gets a CommitFailedException
> --------------------------------------------------
>
>                 Key: OAK-3552
>                 URL: https://issues.apache.org/jira/browse/OAK-3552
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: documentmk
>    Affects Versions: 1.3.7
>            Reporter: Gabriela Matias Navarro
>            Priority: Minor
>              Labels: concurrency, initialization, mongodb
>
> If you start multiple instances of oak pointing to the same mongodb(an empty one), often you get a CommitFailedException in the initialize method from OakInitializer class. That's because two or more instances tries to initialize the collection on mongodb and gets a conflicting on merge. This breaks the initialization on an OSGI environment.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)