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/07/18 22:40:50 UTC

[jira] [Closed] (UIMA-3001) Fix UIMA-AS CAS accounting to prevent loosing CASes

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

Jerry Cwiklik closed UIMA-3001.
-------------------------------

    Resolution: Fixed
    
> Fix UIMA-AS CAS accounting to prevent loosing CASes
> ---------------------------------------------------
>
>                 Key: UIMA-3001
>                 URL: https://issues.apache.org/jira/browse/UIMA-3001
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>    Affects Versions: 2.4.0AS
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.4.1AS
>
>
> In complex scenarios involving many CMs and nested aggregates the uima-as fails to account for CASes correctly. In scenarios where the parent and child flow together, the uima-as can double decrement child count of the ancestor CAS causing it to leave an aggregate while its children are still in play. Such scenario may lead to NullPointerException and a hang.

--
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