[
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-jms-UIMA-786-patch-04-28.txt
uimaj-as-core-UIMA-786-patch-04-28.txt
uimaj-as-activemq-UIMA-786-patch-04-28.txt
Removed hierarchical relationships from CASes. Each CAS is related only to its
top ancestor. The top ancestor is returned back to a client only if *all* of
its children are fully processed. Also assigned state to input CAS to prevent
its release until it reaches the final step or it is dropped due to exceptions.
> 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
> Assignee: Jerry Cwiklik
> Fix For: 2.2.2AS
>
> Attachments: uimaj-as-activemq-UIMA-786-patch-04-28.txt,
> uimaj-as-core-UIMA-786-java-patch.txt,
> uimaj-as-core-UIMA-786-patch-04-28.txt,
> uimaj-as-core-UIMA-786-resources-patch.txt,
> uimaj-as-core-UIMA-786-resources-patch.txt,
> uimaj-as-jms-UIMA-786-patch-04-28.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.
