[jboss-jira] [JBoss JIRA] (WFLY-9417) No default-response-code during deployment sent

[Jason Greene (JIRA)]

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

Jason Greene updated WFLY-9417:
-------------------------------
    Fix Version/s: 13.0.0.Beta1
                       (was: 12.0.0.Final)


> No default-response-code during deployment sent
> -----------------------------------------------
>
>                 Key: WFLY-9417
>                 URL: https://issues.jboss.org/browse/WFLY-9417
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web (Undertow)
>    Affects Versions: 11.0.0.CR1
>            Reporter: Nero M
>            Assignee: Stuart Douglas
>             Fix For: 13.0.0.Beta1
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>
> Hi, i am experiencing a strange behaviour with WF11 which was not like this on WF10.
> When a *.dodeploy file exists during server-start. The Default response code 
> e.g.
> <host name="default-host" alias="localhost" default-response-code="503">
> Is not sent during the time of deployment. Instead any requests goes into a pending state with (seemingly) no timeout.
> If the *.dodeploy file is created AFTER the server boots up, the default response code is sent until the deployment is complete.
> (After this line):  WFLYSRV0025: WildFly Full 11.0.0.CR1 (WildFly Core 3.0.4.Final) started in 6468ms
> I think the server should not "hang" during the deployment-time, just like it was on WF10.
> Is there anything which has to be changed in the standalone xml between 10 and 11 to get the same behaviour?



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)