uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marshall Schor (JIRA)" <uima-...@incubator.apache.org>
Subject [jira] Closed: (UIMA-1400) Uima aggregate with embedded Cas Multiplier fails if one attempts to create multiple instances of it in the same JVM
Date Fri, 02 Oct 2009 20:07:23 GMT

     [ https://issues.apache.org/jira/browse/UIMA-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Marshall Schor closed UIMA-1400.
--------------------------------

    Resolution: Fixed

This is currently working, but impl is forcing users of the CasManager to serialize themselves.
 See UIMA-1598.

> Uima aggregate with embedded Cas Multiplier fails if one attempts to create multiple
instances of it in the same JVM
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-1400
>                 URL: https://issues.apache.org/jira/browse/UIMA-1400
>             Project: UIMA
>          Issue Type: Bug
>          Components: Core Java Framework
>    Affects Versions: 2.2.2
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.3
>
>
> When trying to scale Uima aggregate with a Cas Multiplier in the same JVM, the code fails
with the following:
> org.apache.uima.analysis_engine.AnalysisEngineProcessException: The 
> method CasManager.defineCasPool() was called twice by the same Analysis 
> Engine 
> This is due to the fact that the CasManager creates a single CAS pool for any given Cas
Multiplier, no matter how many instances of it are created. The first instance of a particular
CM creates a CAS Pool and the pool is associated with that instance using a CM's qualified
name obtained from the component's uima context. The second instance of the same CM fails,
since its trying to create another CAS pool with the same qualified name as the first instance.

> Create and assign a unique name in the Uima context for each instance of a component.
Use the unique name when calling defineCasPool() so that every instance of the CM component
creates its own CAS pool.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message