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)" <ui...@incubator.apache.org> on 2009/12/28 23:21:31 UTC

[jira] Commented: (UIMA-1712) Finalize typesystem only when top level aggregate is ready

    [ https://issues.apache.org/jira/browse/UIMA-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794950#action_12794950 ] 

Marshall Schor commented on UIMA-1712:
--------------------------------------

This seems somewhat likely to occur in normal use.  Because of this, and because it seems like a very small fix, I'm leaning to doing a new release candidate for this.  

> Finalize typesystem only when top level aggregate is ready
> ----------------------------------------------------------
>
>                 Key: UIMA-1712
>                 URL: https://issues.apache.org/jira/browse/UIMA-1712
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Eddie Epstein
>            Assignee: Eddie Epstein
>
> a UIMA AS service will finalize its typesystem incorrectly if
>  1. it is an AS-async-aggregate containing a colocated delegate which is itself an async aggregate, AND
>  2. the colocated async aggregate finishes initialization before one of the other top level delegates, AND
>  3. the late top level delegate has new types or new type priorities.
> This can result in initialization errors if a type priority or AE initialization method references a missing 
> type or feature, or an exception later in process() doing the same.
> The bug is caused because the typesystem is finalized when *any* colocated async aggregate finishes
> initialization.

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