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 2011/01/04 23:19:47 UTC

[jira] Updated: (UIMA-1872) UIMA AS Primitive Service ResourceInitializationException is Silently Handled

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

Jerry Cwiklik updated UIMA-1872:
--------------------------------

    Fix Version/s: 2.3.1AS

Assigned Fix Version

> UIMA AS Primitive Service ResourceInitializationException is Silently Handled
> -----------------------------------------------------------------------------
>
>                 Key: UIMA-1872
>                 URL: https://issues.apache.org/jira/browse/UIMA-1872
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>    Affects Versions: 2.3AS
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.3.1AS
>
>
> When deploying Uima AS Primitive service, a custom ThreadFactory is used to initialize each AE instance in its own thread. Once initialized, the AE instance is pinned to its thread. Subsequent process() calls will be done in the same thread that was used to initialize an AE. An exception thrown by AE during initialization propagates all the way to the custom ThreadFactory where it is *silently* ignored. Three bugs here:
> 1) The exception must be logged in the UimaAsThreadFactory.newThread() method.
> 2) Controller's callback listener must be called to notify the listener of initialization exception 
> 3) There is no testcase in extended test suite to expose this bug

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