[jboss-jira] [JBoss JIRA] (WFCORE-3073) Handle TERM gracefully

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474227#comment-13474227 ] 

Brian Stansberry commented on WFCORE-3073:
------------------------------------------

Since a proper attribute isn't really required for the target use case, for now I think I want to defer adding one. I started looking at adding one today and while it's easy to stick an attribute somewhere (e.g. subsystem=core-management), the resource to contain it, the name etc are not blindingly obvious. I don't want to create a half-assed API for just this one attribute and then later we find there are other related attributes for which my half-assed API is a poor fit, and then we need to retrofit.

> Handle TERM gracefully
> ----------------------
>
>                 Key: WFCORE-3073
>                 URL: https://issues.jboss.org/browse/WFCORE-3073
>             Project: WildFly Core
>          Issue Type: Feature Request
>          Components: Domain Management
>            Reporter: Ben Parees
>            Assignee: Brian Stansberry
>             Fix For: 4.0.0.Alpha1
>
>
> The wildfly server currently terminates immediately in response to a TERM signal.  To achieve a clean shutdown requires invoking the CLI tooling.  This is particularly problematic in container environments like kubernetes where the container process (wildfly in this case) is going to get a TERM signal when the container needs to be moved. 
> While it's possible to wrapper the process and handle the TERM and then invoke the CLI, it would be preferable for the server process itself to cleanly handle a TERM signal by waiting for in-flight requests to complete (w/ some grace period of course).
> Having this as configurable behavior would be good if there are backwards compatibility concerns about introducing this behavior change.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)