You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Richard Eckart de Castilho (JIRA)" <de...@uima.apache.org> on 2016/09/01 11:57:20 UTC
[jira] [Updated] (UIMA-5097) Current component info on CAS not
reset
[ https://issues.apache.org/jira/browse/UIMA-5097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Eckart de Castilho updated UIMA-5097:
---------------------------------------------
Summary: Current component info on CAS not reset (was: Possible bug with UimaContextHolder)
> Current component info on CAS not reset
> ---------------------------------------
>
> Key: UIMA-5097
> URL: https://issues.apache.org/jira/browse/UIMA-5097
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Affects Versions: 2.9.0SDK
> Reporter: Richard Eckart de Castilho
> Fix For: 2.9.1SDK
>
>
> There may be a bug that might be related to the UimaContextHolder not being cleaned up probably (probably in case of some kind of failure).
> The problem appears when running the uimafit-core tests in Eclipse. Here all tests run in the same JVM instance which allows "global" information like thread locals to be carried over between unit tests.
> Then running all tests and when the `ViewCreatorAnnotatorTest` runs before the `SimplePipelineTest`, then the deserialization of an XMI file fails because `_InitialView` is still mapped to `myView` in the UIMA context. Debugging yields that the UIMAContext in use for the SimplePipelineTest apparently still belongs to the `ViewCreatorAnnotatorTest` because the *mQualifiedContextName* is `/org.apache.uima.fit.component.ViewCreatorAnnotatorTest$SofaAwareAnnotator/`
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)