[ https://issues.apache.org/jira/browse/UIMA-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor updated UIMA-5547: --------------------------------- Description: The cas complete deserialization done by a test case in UIMA V3 had a strange failure caused by some caching that wasn't cleared (and was holding on to previously created 0-length primitive arrays shared by the JCas). Check all the CAS deserialization paths to insure that non-delta ones do a cas reset - to clear out possibly cached things. And check if extra reset is needed when installing type system, indexes, etc. - some is done in v3, not sure about v2.. was: The cas complete deserialization done by a test case in UIMA V3 had a strange failure caused by some caching that wasn't cleared (and was holding on to previously created DocumentAnnotation feature structure). Check all the CAS deserialization paths to insure that non-delta ones do a cas reset - to clear out possibly cached things (such as the 0-length primitive arrays accessible via the JCas). > some CAS deserializations skipping CAS Reset > -------------------------------------------- > > Key: UIMA-5547 > URL: https://issues.apache.org/jira/browse/UIMA-5547 > Project: UIMA > Issue Type: Bug > Components: Core Java Framework > Reporter: Marshall Schor > Assignee: Marshall Schor > Priority: Minor > Fix For: 3.0.0SDK-beta > > > The cas complete deserialization done by a test case in UIMA V3 had a strange > failure caused by some caching that wasn't cleared (and was holding on to > previously created 0-length primitive arrays shared by the JCas). > Check all the CAS deserialization paths to insure that non-delta ones do a > cas reset - to clear out possibly cached things. And check if extra reset is > needed when installing type system, indexes, etc. - some is done in v3, not > sure about v2.. -- This message was sent by Atlassian JIRA (v6.4.14#64029)