[
https://issues.jboss.org/browse/WFCORE-3073?page=com.atlassian.jira.plugi...
]
Brian Stansberry edited comment on WFCORE-3073 at 7/31/17 5:59 PM:
-------------------------------------------------------------------
Requirement analysis doc for this feature:
https://developer.jboss.org/docs/DOC-56032
Possible implementation is at
https://github.com/wildfly/wildfly-core/compare/master...bstansberry:WFCO.... Manual
use and an integration test shows the suspend logic gets invoked as expected.
was (Author: brian.stansberry):
Requirement analysis doc for this feature:
https://developer.jboss.org/docs/DOC-56032
Possible implementation is at
https://github.com/wildfly/wildfly-core/compare/master...bstansberry:WFCO..., although
that needs an integration test. Manual use shows the suspend logic gets invoked as
expected.
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)