-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
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/7304c019705c5f7ec0378e1c51750432591f73d2
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.
- clones
-
JBEAP-4409 Server processing request isn't stopped immediately but waits for request processing to finish
- Resolved
- is related to
-
WFCORE-1299 IO Subsystem improperly shuts down the worker
- Resolved
- relates to
-
WFLY-3836 Unable to undeploy an application when it is running long time EJB calls.
- Closed