access-log entries might become lost during the shutdown even if graceful timeout is specified ------------------------------------------------------------------------------------------------ Key: WFLY-13933 URL: https://issues.redhat.com/browse/WFLY-13933 Project: WildFly Issue Type: Bug Components: Web (Undertow) Reporter: Masafumi Miura Assignee: Bartosz Baranowski Priority: Major access-log has a possibility to be lost during EAP 7.3 shutdown even if a graceful timeout is specified. If I understand correctly, access-log processing runs on a different thread from the application processing and the graceful shutdown does not care about it. Since EAP 7.3, WFCORE-1632 changed the shutdown behavior to wait only for 100ms (hard-coded). So, EAP 7.3 does not wait for completing a task worker thread processing access-log. I understand the purpose of WFCORE-1632. However, it might be good if we have an option to tune the wait time. (Of course, it would be difficult to know how long wait time is sufficient for completion. And specifying a large wait time can be a cause of long shutdown time. So, it's still questionable how it's useful.) Or, if it's possible to implement that the graceful shutdown can wait for access-log processing, it would be better. (This might be RFE?).