Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-16214

[GSS](7.2.z) WFCORE-4283 - Web management console reports 500 error while domain host controller is in bootup

    XMLWordPrintable

Details

    • +
    • Hide

      0) Use EAP 7.1.4 (7.1.5 should reproduce too), all out-of-box configuration: domain.xml host-master.xml and host-slave.xml
      1) Setup domain master, setup 2 slave hosts, each host has 10(or more) server instances, name these server instances appropriately and setup with appropriate port offset, all server instances marked as auto-start=true.
      2) start master node
      3) start all slave hosts at same time
      4) refresh domain master's web management console "http://master:9990"

      Show
      0) Use EAP 7.1.4 (7.1.5 should reproduce too), all out-of-box configuration: domain.xml host-master.xml and host-slave.xml 1) Setup domain master, setup 2 slave hosts, each host has 10(or more) server instances, name these server instances appropriately and setup with appropriate port offset, all server instances marked as auto-start=true. 2) start master node 3) start all slave hosts at same time 4) refresh domain master's web management console "http://master:9990"

    Description

      ​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.

      Attachments

        1. eap-console-500.png
          eap-console-500.png
          34 kB
        2. failure72.png
          failure72.png
          119 kB
        3. host-slave.xml
          10 kB

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-4283 Web management console reports 500 error while domain host controller is in bootup

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-4557 The read http-upgrade-enabled attribute operation acquires the write lock unnecessarily

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. WFCORE-4381 Intermittent failures of ReadOnlyModeTestCase.testConfigurationNotUpdated

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-17223 [GSS](7.2.z) Upgrade WildFly Core from 6.0.15 to 6.0.16

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Task - Represents a small unit of work that is not end-user facing. JBEAP-17282 (7.2.z) HAL-1618 Support changed lifecycle hosts / servers

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          links to

          Web Link KCS

          Activity

            People

              yborgess1@redhat.com Yeray Borges Santana
              rhn-support-lywang Lyle Wang (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: