[jira] [Comment Edited] (UIMA-3774) make JCasHashMap update thread-safe

["Marshall Schor (JIRA)" <de...@uima.apache.org>]

    [ https://issues.apache.org/jira/browse/UIMA-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13985981#comment-13985981 ] 

Marshall Schor edited comment on UIMA-3774 at 4/30/14 7:55 PM:
---------------------------------------------------------------

improve design by eliminating sync locks in successful read case. Fix issues in comments. move tuning into submaps, and make that work again. have special reserve type. Factor out common "find" process for locating entry.  Have one volatile field in submaps, remove bitsMask from field and recompute from table length always (for consistency in presence of multi-threads). 


was (Author: schor):
improve design by eliminating sync locks in successful read case.

> make JCasHashMap update thread-safe
> -----------------------------------
>
>                 Key: UIMA-3774
>                 URL: https://issues.apache.org/jira/browse/UIMA-3774
>             Project: UIMA
>          Issue Type: Bug
>          Components: Core Java Framework
>    Affects Versions: 2.6.0SDK
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>             Fix For: 2.6.0SDK
>
>
> A recent fix to support multi-thread access in read-only mode to the CAS needs the JCasHashMap to be thread-safe for updates, because 2 or more iterators might simultaneously want to update the map



--
This message was sent by Atlassian JIRA
(v6.2#6252)