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

Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <de...@uima.apache.org> on 2010/09/15 20:55:39 UTC

[jira] Updated: (UIMA-1772) Fix UIMA AS Aggregate Log Entry When Executing Flow Controller step

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

Marshall Schor updated UIMA-1772:
---------------------------------

    Fix Version/s: 2.3.1AS

> Fix UIMA AS Aggregate Log Entry When Executing Flow Controller step
> -------------------------------------------------------------------
>
>                 Key: UIMA-1772
>                 URL: https://issues.apache.org/jira/browse/UIMA-1772
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>    Affects Versions: 2.3AS
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>            Priority: Minor
>             Fix For: 2.3.1AS
>
>
> An entry in the UIMA Log has arguments reversed. It shows CAS id for delegate and delegate key for the CAS Id for log message key: UIMAEE_next_step__FINEST

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