openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (OPENJPA-653) Concurrency issue with query cache enabled
Date Mon, 07 Jul 2008 20:06:31 GMT

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

Michael Dick reassigned OPENJPA-653:
------------------------------------

    Assignee: Jeremy Bauer  (was: Michael Dick)

> Concurrency issue with query cache enabled
> ------------------------------------------
>
>                 Key: OPENJPA-653
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-653
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: datacache
>    Affects Versions: 1.2.0
>            Reporter: Jeremy Bauer
>            Assignee: Jeremy Bauer
>             Fix For: 1.2.0
>
>         Attachments: OPENJPA-653.patch
>
>
> A Java EE application with query result caching enabled and with many concurrent users
is failing with a ConcurrentModificationException in org.apache.openjpa.datacache.QueryCacheStoreQuery.
 Specifically, the failure is in the inner class.method CachingResultObjectProvider.checkFinished(Object,
boolean) and occurs while iterating the _data TreeMap within the QueryResult constructor.
 
> Examination of this method showed that the tree map is synchronized in the beginning
of the method and then later when the  map is cleared in abortCaching().  It is not synchronized
when a new QueryResult is constructed.  This allows a thread to iterate over the map (during
the constructor) while another thread is modifying it.  

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


Mime
View raw message