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 2014/02/21 22:07:19 UTC

[jira] [Updated] (UIMA-3648) UIMA-AS service keeps initializing AEs despite exception

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

Jerry Cwiklik updated UIMA-3648:
--------------------------------

    Description: 
UIMA-AS service uses a custom thread pool factory to allow pining of AEs to specific threads. Initialization of AEs is sequential. It looks like the code is not paying attention to the state of the service before attempting initialization of AE. If AE fails initialization, the code continues to initialize remaining threads instead of stopping the initialization and giving up.

Review the code and make sure the threads dont attempt AE initialization if a previous attempt failed.

Add a new junit test case to test this scenario.


  was:
UIMA-AS service uses a custom thread pool factory to allow pining of AEs to specific threads. Initialization of AEs is sequential. It looks like the code is not paying attention to the state of the service before attempting initialization of AE. If AE fails initialization, the code continues to initialize remaining threads instead of stopping the initialization and giving up.
Review the code and make sure the threads dont attempt AE initialization if a previous attempt failed.


> UIMA-AS service keeps initializing AEs despite exception
> --------------------------------------------------------
>
>                 Key: UIMA-3648
>                 URL: https://issues.apache.org/jira/browse/UIMA-3648
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>    Affects Versions: 2.4.2AS
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.5.0AS
>
>
> UIMA-AS service uses a custom thread pool factory to allow pining of AEs to specific threads. Initialization of AEs is sequential. It looks like the code is not paying attention to the state of the service before attempting initialization of AE. If AE fails initialization, the code continues to initialize remaining threads instead of stopping the initialization and giving up.
> Review the code and make sure the threads dont attempt AE initialization if a previous attempt failed.
> Add a new junit test case to test this scenario.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)