-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
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.
- is duplicated by
-
WFLY-13808 Make HTTP server available during deployment when starting up
- Closed
- is related to
-
WFLY-14750 Batch task not restarted after server resumed from suspended state
- Closed
- relates to
-
WFCORE-1829 Allow server to start in suspended mode
- Resolved
-
WFLY-12329 ManagedScheduledExecutorService should be only available after server is ready
- Resolved
-
WFCORE-4292 Deployment order based on jboss-all.xml doesn't work properly
- Open
-
WFCORE-4594 Expose CoreProcessStateService functionality used by subsystems via a capability
- Closed