[jboss-jira] [JBoss JIRA] (WFCORE-1632) Server processing request isn't stopped immediately but waits for request processing to finish

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262177#comment-13262177 ] 

Brian Stansberry commented on WFCORE-1632:
------------------------------------------

This is an interesting problem. The graceful shutdown timeout was meant to be a limit on how long the server would try and be graceful, but not a limit on how long it would take to stop once it stopped being graceful.

I don't think we should act as if it's a shutdown timeout, at least not without a formal RFE, as that's an open ended commitment. But, still, it's better if it can be closer to that.

I haven't looked closely at the link in the description, but I figure it's ultimately about using a shared thread pool that is depended upon but not controlled by the webserver instead of using one that the webserver itself shuts down.

> 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/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.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)