[
https://issues.apache.org/jira/browse/UIMA-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677488#action_12677488
]
Burn Lewis commented on UIMA-1297:
----------------------------------
We've discussed an "optimization" that would immediately execute the error
handling as if a timeout had occurred (since that's what would happen if the
request was lost later in the network) but decided to postpone that for now
until we understand its impact on the new single-timer-per-delegate
implementation.
> Uima AS Service Not Handling Send Failures Correctly
> ----------------------------------------------------
>
> Key: UIMA-1297
> URL: https://issues.apache.org/jira/browse/UIMA-1297
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
>
> When a send requst fails due to a lost broker connection, the uima AS
> aggregate removes the CAS from the outstanding list. Subsequently, when a
> timer pops the Timeout Exception is reported against the wrong CAS.
> Fix the code so that the CAS remains in the outstanding list until the timer
> pops.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
