-
Bug
-
Resolution: Done
-
Major
-
7.1.4.GA
In EAP 7.1 domain setup, web management console executes the op `:read-children-resources(child-type=host)` when it starts. A host controller triggers managed server instances startup sequentially (SERVER_STOPPED to SERVER_STARTING) which may take some very long time for host controller to finish boot process (when there are dozens of managed server instances). And in this case `:read-children-resources(child-type=host)` operation could fail with 500 error when using web management console on domain master node. Resulting in the web console becomes un-usable for long time.
The operation `:read-children-resources(child-type=host)` needs a fix to avoid 500 error.
The web management console should start up as soon as the domain controller (master node) is available. Hosts and servers in the topology view should show up as soon as they're available.
- clones
-
WFCORE-4283 Web management console reports 500 error while domain host controller is in bootup
- Closed
-
WFCORE-4557 The read http-upgrade-enabled attribute operation acquires the write lock unnecessarily
- Closed
-
WFCORE-4381 Intermittent failures of ReadOnlyModeTestCase.testConfigurationNotUpdated
- Resolved
- is incorporated by
-
JBEAP-17223 [GSS](7.2.z) Upgrade WildFly Core from 6.0.15 to 6.0.16
- Closed
- is related to
-
JBEAP-17282 (7.2.z) HAL-1618 Support changed lifecycle hosts / servers
- Closed
- links to