uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry Cwiklik (JIRA)" <...@uima.apache.org>
Subject [jira] [Updated] (UIMA-3905) UIMA-AS should not be using System.exit()
Date Tue, 08 Dec 2015 16:49:11 GMT

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

Jerry Cwiklik updated UIMA-3905:
    Fix Version/s:     (was: 2.8.1AS)

> UIMA-AS should not be using System.exit()
> -----------------------------------------
>                 Key: UIMA-3905
>                 URL: https://issues.apache.org/jira/browse/UIMA-3905
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.8.2AS
> There are a few places where UIMA-AS calls System.exit(). This should be removed and
a different approach is needed to force the cleanup. 
> In one scenario, the UIMA-AS terminates when configured error threshold is reached for
AE. In another, the UIMA-AS catches java Error like OOM .
> If the UIMA-AS is deployed in a Tomcat container for example the exit() kills the jvm
which is a big issue. 
> To support embedding in applications, the UIMA-AS must provide a better way to deal with
termination state. One possible approach could be to notify the service wrapper/container
that a fatal state has been detected and have the container call stop to clean things up.

This message was sent by Atlassian JIRA

View raw message