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

(7.3.z) When using Galleon to provision EAP with core-server+managment layers, the availability of the Admin console is wrongly advertised to the user

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.3.3.CR1, 7.3.3.GA
    • 7.3.2.CR1
    • Management
    • None
    • +
    • Hide

      1. get Galleon CLI: https://github.com/wildfly/galleon/releases/tag/4.2.5.Final
      2. unzip it && cd to bin
      3. add the path to $PATH or just run the script locally (./galleon.sh)
      4. at the prompt type install wildfly:current --dir=custom-serv --layers=core-server,management
      5. from another shell cd to the "custom-serv" dir
      6. start the server (./bin/standalone.sh) and look at the log.
      7. try to reach http://127.0.0.1:9990 or http://127.0.0.1:9990/console, you should get a HTTP 404, while http://127.0.0.1:9990/management is working

      Show
      1. get Galleon CLI: https://github.com/wildfly/galleon/releases/tag/4.2.5.Final 2. unzip it && cd to bin 3. add the path to $PATH or just run the script locally ( ./galleon.sh ) 4. at the prompt type install wildfly:current --dir=custom-serv --layers=core-server,management 5. from another shell cd to the "custom-serv" dir 6. start the server (./bin/standalone.sh) and look at the log. 7. try to reach http://127.0.0.1:9990 or http://127.0.0.1:9990/console , you should get a HTTP 404, while http://127.0.0.1:9990/management is working

    Description

      NOTE: the description below is in the WildFly context and focuses on Galleon slimming and specific layers WildFly supports but which in EAP are details. But the flaw is a general one not specific to Galleon slimming. Users manually slimming a server (which would be easy to do if the large console wasn't wanted) would see the same problem. I suspect the Galleon slimming we support in s2i would also see this issue, as I assume we are not going out of our way to add in the console, which is large and not really useful in an image.

      The original report:

      When using Galleon to provision a Wildfly instance which would include just the core-server and managment layers, the LOG will trace the following lines:

      ...
15:38:17,219 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 20.0.1.Final (WildFly Core 12.0.3.Final) started in 1625ms - Started 86 of 89 services (27 services are lazy, passive or on-demand)
15:38:17,221 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
15:38:17,221 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990

      This is a wrong message for the end user because the managment interface will be available at the reported URL but the Admin console won't, returning a HTTP 404 status code.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-5073 When using Galleon to provision Wildfly with core-server+managment layers, the availability of the Admin console is wrongly advertised to the user

          • 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

          Activity

            People

              chaowan@redhat.com Chao Wang
              fburzigo Fabio Burzigotti
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: