You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org> on 2013/08/20 22:16:52 UTC

[jira] [Closed] (UIMA-3155) UIMA-AS should support using timer for each outstanding CAS

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

Jerry Cwiklik closed UIMA-3155.
-------------------------------

    Resolution: Fixed

To enable timer per CAS add TimerPerCAS to the Map to be passing as an arg to the client initialize method
                
> UIMA-AS should support using timer for each outstanding CAS 
> ------------------------------------------------------------
>
>                 Key: UIMA-3155
>                 URL: https://issues.apache.org/jira/browse/UIMA-3155
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Async Scaleout
>    Affects Versions: 2.4.0AS
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.4.2AS
>
>
> Currently, UIMA-AS uses a single timer manage CAS timeouts. Extend the code to support per CAS timer. This would only be enabled on demand via UIMA-AS Client property included in a Map that is used to initialize the client. The default will remains to be a single timer for all outstanding CASes. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira