]
Radim Hatlapatka commented on WFCORE-1632:
------------------------------------------
The issue isn't with graceful shutdown as such, the issue is with server stopping. The
server stopping hangs and waits for request processing to finish. If the server was doing
some long time processing the only way to shut him down is by forcibly killing it instead
of being just stopped in timely manner.
Note currently the processing which is done is completely pointless as there is no way to
deliver the result in such case as the connection itself was destroyed. So there is done
processing which is then thrown away.
Server processing request isn't stopped immediately but waits for
request processing to finish
----------------------------------------------------------------------------------------------
Key: WFCORE-1632
URL:
https://issues.jboss.org/browse/WFCORE-1632
Project: WildFly Core
Issue Type: Bug
Components: Domain Management, IO, Server
Reporter: Lin Gao
Assignee: Lin Gao
Priority: Critical
Original Estimate: 1 day
Remaining Estimate: 1 day
When stopping server which is processing request, it terminates the connection from the
client but doesn't stop the request processing as such.
After debugging and searching when the issue appeared I've found out that the issue
was introduced with this commit:
[
https://github.com/wildfly/wildfly-core/commit/7304c019705c5f7ec0378e1c51...]
Steps to reproduce:
1) start EAP server with deployed app from attachment
2) create request to long running application: {{curl -i
http://127.0.0.1:8080/long-running-servlet/HeavyProcessing?duration=25000}}
3) stop server (you can do it even gracefully) using {{./jboss-cli.sh -c
":shutdown(timeout=1)"}}
See that server is stopped after 25 seconds since request from step 2 was issued, as that
is duration of the request processing requested by param duration, instead of being
terminated after 1 second.