[jira] Updated: (UIMA-1223) Annotators should be initialized in the same thread that their process method will later be called on

["Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>]

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

Jerry Cwiklik updated UIMA-1223:
--------------------------------

    Attachment: uimaj-as-core-UIMA-1223-patch.txt
                uimaj-as-activemq-UIMA-1223-patch.txt

Added custom Thread factory to the ThreadPoolTaskExecutor that creates threads which  Initialize AEs in a primitive controller. Subsequently, a thread that initialized AE will be called to call process method on that AE instance. Modified primitive controller to create resource specifier in the same thread that will create AE instance.

Modified UimaDefaultMessageListenerContainer, to wait for all threads to stop.

> Annotators should be initialized in the same thread that their process method will later be called on
> -----------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-1223
>                 URL: https://issues.apache.org/jira/browse/UIMA-1223
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>    Affects Versions: 2.2.2
>            Reporter: Adam Lally
>            Assignee: Jerry Cwiklik
>         Attachments: uimaj-as-activemq-UIMA-1223-patch.txt, uimaj-as-core-UIMA-1223-patch.txt
>
>
> It is more convenient if an annotator is initialized on the same thread that it is later called on.  Some components may use thread-local data and they won't work in UIMA-AS currently.  Another advantage of doing the initialization in the processing thread is that you could initialize multiple instances of the annotator in parallel instead of sequentially, which may be faster for a multi-core machine.

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