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 E949C10AE8 for ; Thu, 29 Aug 2013 15:19:57 +0000 (UTC) Received: (qmail 62260 invoked by uid 500); 29 Aug 2013 15:19:57 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 61833 invoked by uid 500); 29 Aug 2013 15:19:56 -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 61502 invoked by uid 99); 29 Aug 2013 15:19:54 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Aug 2013 15:19:54 +0000 Date: Thu, 29 Aug 2013 15:19:54 +0000 (UTC) From: "Marcel Reutegger (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 ] Marcel Reutegger updated JCR-3658: ---------------------------------- Attachment: JCR-3658-test.patch Attached patch illustrates the issue with the synchronization. > 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.7 > Reporter: Tobias Bocanegra > Assignee: Marcel Reutegger > Priority: Minor > Attachments: JCR-3658-test.patch > > > 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 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