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 2018/11/26 17:58:00 UTC

[jira] [Closed] (UIMA-5909) UIMA-AS: Make Shutdown hooks optional

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

Jerry Cwiklik closed UIMA-5909.
-------------------------------
       Resolution: Fixed
         Assignee: Jerry Cwiklik
    Fix Version/s: 2.10.4AS

Modified to disable UIMA-AS ShutdownHook if -DDISABLE_SHUTDOWN_HOOK  property is defined

> UIMA-AS: Make Shutdown hooks optional
> -------------------------------------
>
>                 Key: UIMA-5909
>                 URL: https://issues.apache.org/jira/browse/UIMA-5909
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Async Scaleout
>    Affects Versions: 2.10.2AS
>            Reporter: Patrick Huy
>            Assignee: Jerry Cwiklik
>            Priority: Major
>             Fix For: 2.10.4AS
>
>
> In BaseUIMAAsynchronousEngine_impl a shutdown hook gets added to the Runtime which stops the AsynchronousEngine. This makes it impossible for consumers to correclty implement a graceful shutdown behaviour on JVM shutdow.
>  
> For applications running on Kubernetes the expectation is that on "SIGTERM" the application completes running requests and then exits. SIGTERM also triggers JVM shutdown hooks, the AS shutdown hooks prevent running requests from completing (because the AS Engine is stopped).
> It also seems like these hooks are never removed which might lead to issues if a lot of AS Engines are initialized.
> It would be benefitial to make these shutdown hooks optional or remove them outright.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)