Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <9602759.1177680916588.JavaMail.jira@brutus>
Date: Fri, 27 Apr 2007 06:35:16 -0700 (PDT)
From: "Stefan Guggisberg (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Resolved: (JCR-862) unsynchronized access on 'itemCache' map
 in ItemManager
In-Reply-To: <23946339.1177421415546.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Stefan Guggisberg resolved JCR-862.
-----------------------------------

    Resolution: Fixed

fixed in svn r533091

> unsynchronized access on 'itemCache' map in ItemManager 
> --------------------------------------------------------
>
>                 Key: JCR-862
>                 URL: https://issues.apache.org/jira/browse/JCR-862
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.2.3
>            Reporter: Tobias Bocanegra
>         Assigned To: Stefan Guggisberg
>             Fix For: 1.4
>
>
> the access 'itemCache' map in ItemManager is mostly synchronized by not via the ItemStateListener methods:
> [...]
>     public void stateCreated(ItemState created) {
>         ItemImpl item = retrieveItem(created.getId());
>         if (item != null) {
>             item.stateCreated(created);
>         }
>     }
> [...]
>     private ItemImpl retrieveItem(ItemId id) {
>         return (ItemImpl) itemCache.get(id);
>     }
> [...]
> this can result in a corruption of a map (eg subsequent accesses may result in a endless loop).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.