Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <1363200182.1257804692417.JavaMail.jira@brutus>
Date: Mon, 9 Nov 2009 22:11:32 +0000 (UTC)
From: "Rick Curtis (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Closed: (OPENJPA-1379) Locking problem when using timestamp
 QueryCache eviction policy.
In-Reply-To: <94718484.1257799712640.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Rick Curtis closed OPENJPA-1379.
--------------------------------

    Resolution: Fixed

This issue is fixed in trunk.

> Locking problem when using timestamp QueryCache eviction policy.
> ----------------------------------------------------------------
>
>                 Key: OPENJPA-1379
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1379
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: datacache
>    Affects Versions: 2.0.0-M3
>            Reporter: Rick Curtis
>            Assignee: Rick Curtis
>             Fix For: 2.0.0-M4
>
>
> I ran into a bug in AbstractQueryCache when using the timestamp QueryCache eviction policy. This is only a problem when running in a multithreaded environment.
> The net of the problem is that in AbstractQueryCache.onTypesChanged(TypesChangedEvent ev) we call writeLock(), but when using the non-default eviction policy we never call writeUnlock(). As a result, any other threads requesting a writeLock on the cache will block indefinitely.

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