[
https://issues.apache.org/jira/browse/UIMA-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik updated UIMA-786:
-------------------------------
Attachment: uimaj-as-core-UIMA-786-resources-patch.txt
uimaj-as-core-UIMA-786-java-patch.txt
Modified uima-as core to hold on to the input (parent) CAS until all of its
subordinate CASes are fully processed. When all subordinate CASes are
processed, the aggregate service will return the input CAS back to the client.
> Input CAS is returned back to the client while subordinate CASes are still in
> play in the aggregate
> ---------------------------------------------------------------------------------------------------
>
> Key: UIMA-786
> URL: https://issues.apache.org/jira/browse/UIMA-786
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.2.1
> Reporter: Jerry Cwiklik
> Attachments: uimaj-as-core-UIMA-786-java-patch.txt,
> uimaj-as-core-UIMA-786-resources-patch.txt
>
>
> When an input CAS is returned from a Cas Multiplier, an Aggregate immediately
> returns it back to the client with no check if the subordinate CASes (those
> produced from the input CAS) are still in "in-play" in other delegates. Upon
> receiving the input CAS reply, the client assumes success and sends a CPC.
> Meanwhile, the CASes still in-play may cause Exceptions and termination of
> the
> aggregate. The CPC sent to the service may never be replied to leading to a
> hang.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
