You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org> on 2009/07/22 19:55:14 UTC
[jira] Created: (UIMA-1450) UIMA AS controller creates a component
CAS Pool with a wrong name
UIMA AS controller creates a component CAS Pool with a wrong name
-----------------------------------------------------------------
Key: UIMA-1450
URL: https://issues.apache.org/jira/browse/UIMA-1450
Project: UIMA
Issue Type: Bug
Components: Async Scaleout
Reporter: Jerry Cwiklik
Assignee: Jerry Cwiklik
The Uima AS controller incorrectly names a CAS Pool during initialization. It uses qualifiedContextName instead of a unique name. The core fix UIMA-1400 broke the UIMA AS to the extent that the CM is always given a Cas Pool of 1 leading to a performance problem. In initializeComponentCasPool() method use getComonentName() call to define the CAS Pool.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1450) UIMA AS controller creates a component
CAS Pool with a wrong name
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik closed UIMA-1450.
-------------------------------
Resolution: Fixed
Modified base controller code to call getUniqueName() on the UimaContext object to fetch a name of the Cas Pool for the Cas Multipler.
> UIMA AS controller creates a component CAS Pool with a wrong name
> -----------------------------------------------------------------
>
> Key: UIMA-1450
> URL: https://issues.apache.org/jira/browse/UIMA-1450
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
>
> The Uima AS controller incorrectly names a CAS Pool during initialization. It uses qualifiedContextName instead of a unique name. The core fix UIMA-1400 broke the UIMA AS to the extent that the CM is always given a Cas Pool of 1 leading to a performance problem. In initializeComponentCasPool() method use getComonentName() call to define the CAS Pool.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1450) UIMA AS controller creates a component
CAS Pool with a wrong name
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-1450:
--------------------------------
Fix Version/s: 2.3AS
> UIMA AS controller creates a component CAS Pool with a wrong name
> -----------------------------------------------------------------
>
> Key: UIMA-1450
> URL: https://issues.apache.org/jira/browse/UIMA-1450
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.3AS
>
>
> The Uima AS controller incorrectly names a CAS Pool during initialization. It uses qualifiedContextName instead of a unique name. The core fix UIMA-1400 broke the UIMA AS to the extent that the CM is always given a Cas Pool of 1 leading to a performance problem. In initializeComponentCasPool() method use getComonentName() call to define the CAS Pool.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.