[
https://issues.apache.org/jira/browse/UIMA-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749247#action_12749247
]
Marshall Schor edited comment on UIMA-1400 at 9/11/09 5:53 AM:
---------------------------------------------------------------
If UIMA-1223 did not make the thread-safety issue raised by Joern above moot,
then I'm +1 for fixing the thread saftey issue and maybe also UIMA-1249, for
the 2.3.0 release, because this kind of issue (if it happens) becomes very hard
to track down, and could impact our "reputation".
was (Author: schor):
If UIMA-1233 did not make the thread-safety issue raised by Joern above
moot, then I'm +1 for fixing the thread saftey issue and maybe also UIMA-1249,
for the 2.3.0 release, because this kind of issue (if it happens) becomes very
hard to track down, and could impact our "reputation".
> 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.
