Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Wed, 17 Apr 2013 13:51:16 +0000 (UTC)
From: "Marcel Reutegger (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <JIRA.12642930.1366206531764.180113.1366206676447@arcas>
In-Reply-To: <JIRA.12642930.1366206531764@arcas>
References: <JIRA.12642930.1366206531764@arcas>
Subject: [jira] [Updated] (JCR-3573) Improve token based login concurrency
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Marcel Reutegger updated JCR-3573:
----------------------------------

    Status: Patch Available  (was: Open)
    
> Improve token based login concurrency
> -------------------------------------
>
>                 Key: JCR-3573
>                 URL: https://issues.apache.org/jira/browse/JCR-3573
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Marcel Reutegger
>            Priority: Minor
>         Attachments: JCR-3573.patch
>
>
> Currently TokenBasedAuthentication.createToken() is synchronized and therefore serializes creation of tokens repository wide.
> Removing the synchronization shows test failures because the .tokens node is created concurrently by multiple sessions. Instead of serializing the calls, we could also use an optimistic approach. See attached patch. All tests pass.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira