[jboss-jira] [JBoss JIRA] (WFLY-5162) Graceful shutdown on server group doesn't take into account timeout

[Radim Hatlapatka (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-5162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radim Hatlapatka moved JBEAP-812 to WFLY-5162:
----------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-5162  (was: JBEAP-812)
             Workflow: GIT Pull Request workflow   (was: CDW v1)
    Affects Version/s: 10.0.0.Beta1
                           (was: EAP 7.0.0.DR8)
          Component/s: Server
                       Web (Undertow)
                           (was: Server)
                           (was: Web (Undertow))
       Target Release:   (was: EAP 7.0.0.GA)


> Graceful shutdown on server group doesn't take into account timeout
> -------------------------------------------------------------------
>
>                 Key: WFLY-5162
>                 URL: https://issues.jboss.org/browse/WFLY-5162
>             Project: WildFly
>          Issue Type: Bug
>          Components: Server, Web (Undertow)
>    Affects Versions: 10.0.0.Beta1
>            Reporter: Radim Hatlapatka
>            Assignee: Stuart Douglas
>            Priority: Critical
>         Attachments: long-running-servlet.war
>
>
> The timeout for graceful shutdown in case of domain server groups isn't respected.
> Steps to reproduce
> # start server in domain (domain.sh)
> # Deploy application which allows creating long running requests (you can use the one provided in attachment)
> # Create request to server-one (in main server group), which shall take longer time then graceful shutdown for example 50s ({{curl -v http://127.0.0.1:8080/long-running-servlet/HeavyProcessing?duration=50000}})
> # In the mean time call graceful shutdown on main server group ({{/server-group=main-server-group:stop-servers(timeout=5)}})
> The request should be terminated by server after 5s, still it is fully processed with 200 status code.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)