]
Brian Stansberry commented on WFLY-10315:
-----------------------------------------
Can you describe your use case further? The configuration service must be started or it
doesn't provide a useful response. So are there other deployments on the same server
that are delaying things?
Or, perhaps this is a request for the server to not block incoming requests while waiting
for graceful startup, but rather to respond immediately with an error response? If so
there is a separate RFE for that:
Restore legacy (not "graceful") startup mode
--------------------------------------------
Key: WFLY-10315
URL:
https://issues.jboss.org/browse/WFLY-10315
Project: WildFly
Issue Type: Feature Request
Reporter: Vladimir Grabarchuk
Assignee: Jason Greene
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.