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 2021/11/08 08:46:00 UTC

[jira] [Commented] (UIMA-5058) Scaled out pipelines can falsely trigger the error: Illegal adding of additional MetaData after CASes have been defined

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

Richard Eckart de Castilho commented on UIMA-5058:
--------------------------------------------------

Looks like some of the changes for this issue were filed under another issue ID. E.g. the unit tests for this issue seem to be under UIMA-5043, e.g. commit 4b7382227a38412a7fb6987ea7e3b0d86c64ce2a.

> Scaled out pipelines can falsely trigger the error: Illegal adding of additional MetaData after CASes have been defined
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-5058
>                 URL: https://issues.apache.org/jira/browse/UIMA-5058
>             Project: UIMA
>          Issue Type: Bug
>          Components: Core Java Framework
>    Affects Versions: 2.8.1SDK
>            Reporter: Burn L. Lewis
>            Assignee: Marshall Schor
>            Priority: Major
>             Fix For: 2.9.0SDK, 3.0.0SDK-alpha02
>
>
> When UIMA-AS scales out a synchronous UIMA pipeline it sequentially creates separate AEs in separate threads, sharing the resource manager.  Creation of the 2nd (identical) AE will fail with "Illegal adding of additional MetaData after CASes have been defined" if a descriptor imports 2 type-system files, one of which is included in the other.  The check fails to recognize that the types loaded by the 2nd AE are already in the resource manager because of the way type-systems are cached.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)