Brian Stansberry created WFCORE-5077:
----------------------------------------
Summary: When using Galleon to provision Wildfly with core-server+managment
layers, the availability of the Admin console is wrongly advertised to the user
Key: WFCORE-5077
URL:
https://issues.redhat.com/browse/WFCORE-5077
Project: WildFly Core
Issue Type: Bug
Components: Management
Affects Versions: 12.0.2.Final, 13.0.0.Beta2
Reporter: Fabio Burzigotti
Assignee: Brian Stansberry
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:
{code}
...
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
{code}
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.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)