[jira] [Updated] (UIMA-3672) UIMA-AS client should support configurable timer strategies to timeout CASes

["Jerry Cwiklik (JIRA)" <de...@uima.apache.org>]

     [ https://issues.apache.org/jira/browse/UIMA-3672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik updated UIMA-3672:
--------------------------------
    Fix Version/s:     (was: 2.8.1AS)
                   2.8.2AS

> UIMA-AS client should support configurable timer strategies to timeout CASes
> ----------------------------------------------------------------------------
>
>                 Key: UIMA-3672
>                 URL: https://issues.apache.org/jira/browse/UIMA-3672
>             Project: UIMA
>          Issue Type: New Feature
>          Components: Async Scaleout
>    Affects Versions: 2.4.2AS
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.8.2AS
>
>
> Currently, the UIMA-AS client uses a single timer to time outstanding CASes.
> The main disadvantage of this is that timeouts are serial. If say two CASes are outstanding, the first CAS will timeout, the timer is restarted, and the second CAS times out. 
> The timeout should be associated with processing more closely. It seems that the client should support per CAS timer that will be started as soon as the confirmation comes from a service that is ready to process the CAS. It has been observed that on rare occasions under heavy load the confirmations or getting lost which needs to be taken into an account when designing a new approach. So far the reason for missing a confirmation message is not known.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)