[jboss-jira] [JBoss JIRA] (WFCORE-4291) Restore legacy (not "graceful") startup mode

[Brian Stansberry (Jira)]

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

Brian Stansberry reassigned WFCORE-4291:
----------------------------------------

    Forum Reference: https://lists.jboss.org/pipermail/wildfly-dev/2019-July/006943.html
           Assignee: Brian Stansberry


[~vladchuk2] I'm taking a look at this for WF 18 or 19.

See https://lists.jboss.org/pipermail/wildfly-dev/2019-July/006943.html

> Restore legacy (not "graceful") startup mode
> --------------------------------------------
>
>                 Key: WFCORE-4291
>                 URL: https://issues.jboss.org/browse/WFCORE-4291
>             Project: WildFly Core
>          Issue Type: Feature Request
>          Components: Management
>            Reporter: Vladimir Grabarchuk
>            Assignee: Brian Stansberry
>            Priority: Major
>
> Please allow a configurable legacy startup mode which was the default before WF11, when components can service HTTP requests as soon as they are deployed, not when the container deploys all components.
> The use case for this is the following: there is a configuration service component upon which other components depend for configuration data, requested and served via a HTTP request. With the new "graceful startup" this scenario no longer seems possible,  as it results in read timeouts, mis-configured artifacts, and failed deployments altogether.
> If generally feasible, another value of the *--start-mode=legacy* seems appropriate to accommodate the original (legacy) behavior.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)