[
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.
