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 2008/12/17 18:13:44 UTC

[jira] Updated: (UIMA-1255) Modify UIMA-AS Aggregate to Handle Cas Not Found Error

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

Jerry Cwiklik updated UIMA-1255:
--------------------------------

    Attachment: uimaj-as-core-UIMA-1255-patch.txt

Handles Cas Not Found in the finalStep() of the Uima AS Aggregate. The exception is logged and the code returns immediately. This exception is not send back to the client.

> Modify UIMA-AS Aggregate to Handle Cas Not Found Error
> ------------------------------------------------------
>
>                 Key: UIMA-1255
>                 URL: https://issues.apache.org/jira/browse/UIMA-1255
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>         Attachments: uimaj-as-core-UIMA-1255-patch.txt
>
>
> Catch Cas Not Found exception in the finalStep(), log it and return. This exception can occur when one thread is processing a child of an input CAS in parallel with another thread processing a second child of the same CAS. The first thread may remove the input CAS before the second thread completes.
> When this happens, the second thread eventually will try to fetch the input CAS but by that time the CAS no longer exists. An exception is thrown and send through the error handler which reports it to a client. This exception should be handled by the aggregate and not sent to the client.

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