[
https://issues.apache.org/jira/browse/UIMA-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15853841#comment-15853841
]
Richard Eckart de Castilho commented on UIMA-5058:
--------------------------------------------------
I'm leaving this open because a "null" tsp vs a "default" tsp may not be an
uncommon case.
However, I also come to the conclusion that there is a more fundamental thing
going on related to the introduction of the UimaContextHolder and will bring
that up on the mailing list.
> 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 Lewis
> Assignee: Burn Lewis
> Fix For: 2.9.0SDK, 3.0.0SDK-alpha
>
>
> 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
(v6.3.15#6346)
