[
https://issues.apache.org/jira/browse/UIMA-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik updated UIMA-1117:
--------------------------------
Attachment: uimaj-as-core-UIMA-1117.txt
When processing an exception received from a delegate configured with
continueOnError=true, the error handler in the Aggregate AS service deletes a
client endpoint from the OriginMap. The CAS is then processed by down stream
annotators and eventually reaches the final step. Since the origin of the CAS
has been deleted, the Aggregate does not know where to send the reply. Removed
the erronoeus code that deleted the origin of the CAS.
> Simple aggregate hangs when get a delegate error on an input CAS
> ----------------------------------------------------------------
>
> Key: UIMA-1117
> URL: https://issues.apache.org/jira/browse/UIMA-1117
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.2.2
> Reporter: Burn Lewis
> Fix For: 2.2.2AS
>
> Attachments: UIMA-1117.patch, uimaj-as-core-UIMA-1117.txt
>
>
> If continueOnRetryFailure is true for a delegate that reports an error, the
> CAS continues to the end of the aggregate but is not returned to the client
> or to the pool. When it is false the exception is returned correctly. This
> only fails for original input CASes ... error handling works correctly for
> CASes created by a CR or CM inside the aggregate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
