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)" <ui...@incubator.apache.org> on 2009/11/16 18:31:39 UTC

[jira] Closed: (UIMA-1665) UIMA AS aggregate not handling timeouts correctly for parallel delegates

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

Jerry Cwiklik closed UIMA-1665.
-------------------------------

    Resolution: Fixed

Modified UIMA AS error handling code to prevent double counting delegates responded while handling timeouts in parallel step. Added new testcase testMutlipleDelegateTimeoutsInParallelFlows() to test the scenario.

> UIMA AS aggregate not handling timeouts correctly for parallel delegates
> ------------------------------------------------------------------------
>
>                 Key: UIMA-1665
>                 URL: https://issues.apache.org/jira/browse/UIMA-1665
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Priority: Blocker
>             Fix For: 2.3AS
>
>
> Burn discovered a bug in UIMA AS aggregate while handling timeouts from delegates in a parallel step. A delegate timeout that is subsequently disabled (due to error handling setting action=disable), causes error handling code to (incorrectly) double increment the count of delegates that responded. The count is maintained to determine how many delegates in a parallel step responded and if it is ok to allow the CAS to continue with the flow. This counter is incremented when a reply comes or there is a timeout. When the counter reaches the expected number, the CAS is allowed to continue on with flow. The double increment causes a CAS to continue in the flow prematurely. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.