Return-Path: X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A459310A86 for ; Tue, 8 Oct 2013 03:35:55 +0000 (UTC) Received: (qmail 78100 invoked by uid 500); 8 Oct 2013 03:35:27 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 77892 invoked by uid 500); 8 Oct 2013 03:35:12 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 77769 invoked by uid 99); 8 Oct 2013 03:34:54 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Oct 2013 03:34:54 +0000 Date: Tue, 8 Oct 2013 03:34:54 +0000 (UTC) From: "Jukka Zitting (JIRA)" To: dev@jackrabbit.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (JCR-3658) MembershipCache not consistently synchronized MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/JCR-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-3658: ------------------------------- Fix Version/s: (was: 2.4.4) 2.4.5 > MembershipCache not consistently synchronized > --------------------------------------------- > > Key: JCR-3658 > URL: https://issues.apache.org/jira/browse/JCR-3658 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: jackrabbit-core, security > Affects Versions: 2.4.3, 2.6.3, 2.7 > Reporter: Tobias Bocanegra > Assignee: Marcel Reutegger > Priority: Minor > Fix For: 2.4.5, 2.6.4, 2.7.1 > > Attachments: current.png, JCR-3658.patch, JCR-3658.patch, JCR-3658-test.patch, patched.png > > > the membership cache access is mostly synchronized on 'this' but in the onEvent() handler, the internal cache object is synchronized. > suggest: to improve cache access by a r/w lock instead. -- This message was sent by Atlassian JIRA (v6.1#6144)