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 2008/04/11 19:36:04 UTC
[jira] Updated: (UIMA-983) Collocated UIMA-AS Aggregate sends
invalid CAS id in a reply msg
[ https://issues.apache.org/jira/browse/UIMA-983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-983:
-------------------------------
Attachment: uimaj-as-core-UIMA-983-patch.txt
Modified finalStep() method of an Aggregate AS Service to reply to its parent with the correct CasReference Id. Fixes a reported hang in the top level UIM-AS Aggregate
> Collocated UIMA-AS Aggregate sends invalid CAS id in a reply msg
> ----------------------------------------------------------------
>
> Key: UIMA-983
> URL: https://issues.apache.org/jira/browse/UIMA-983
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Fix For: 2.2.2AS
>
> Attachments: uimaj-as-core-UIMA-983-patch.txt
>
>
> A collocated UIMA-AS aggregate in its finalStep() method sends an invalid CasReferenceId in a reply msg. Instead of sending an Id of the subordinate CAS it sends an Id of the Input CAS from which the subordinate was produced. This confuses the parent Aggregate and CASes are not cleared from the InProcessCache resulting in a hang.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.