[
https://issues.apache.org/jira/browse/UIMA-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik closed UIMA-2461.
-------------------------------
Resolution: Fixed
Assignee: Jerry Cwiklik
During initialization, the UIMA AS forces creation of a cas pool for each of
its CMs. This is done to register a CM MBean with JMX, so that the cas pool
configuration is visible in jConsole. For uima aggregate CM, cas pools are
opaque and not accessible to UIMA AS. Each internal CM, has its own cas pool
that is created and initialized by the ASB. Modified uima-as code to not force
creation of a cas pool for uima aggregate CM.
> UIMA AS doesnt support deployment of colocated uima aggregate CM
> ----------------------------------------------------------------
>
> Key: UIMA-2461
> URL: https://issues.apache.org/jira/browse/UIMA-2461
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.4.0AS
>
>
> When deploying a co-located uima aggregate CM (async=false), the UIMA-AS
> throws an exception caused by:
> org.apache.uima.aae.error.AsynchAEException:
> org.apache.uima.UIMARuntimeException: AnalysisComponent "/<aggregate
> component>/" requested more CASes (1) than defined in its
> getCasInstancesRequired() method (0). It is possible that the
> AnalysisComponent is not properly releasing CASes when it encounters an error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
