[
https://issues.jboss.org/browse/WFCORE-3073?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-3073:
------------------------------------------
[~swd847] I get into that a bit in the analysis doc. The main use case for this is things
like OpenShift. I don't see them wanting to mess with management API or our xml to
configure this. And even something like putting an attribute in our standard config but
with an expression with this property as the value makes it something that may or may not
work, depending on whether the user retains that attribute in their xml.
So I figured
1) -1 to *requiring* a proper management attribute; i.e. not supporting directly reading a
property in the runtime.
2) Adding a proper attribute, and only falling back to the property if the attribute is
not set is fine. But I can come back to that later. I wanted to do the quick part first,
in case someone got excited and pushed to get this in ASAP.
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.2.3#72005)