[jboss-jira] [JBoss JIRA] (WFCORE-2771) Wildfly Management Console should log bound ports

Jason Tedor (JIRA) issues at jboss.org
Sat May 6 23:30:00 EDT 2017


     [ https://issues.jboss.org/browse/WFCORE-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Tedor updated WFCORE-2771:
--------------------------------
    Description: 
When binding Wildfly Management Console to an ephemeral port (i.e., by specifying port 0), Wildfly states that the management console:

{code}
23:15:55,138 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0063: Http management interface is not enabled
23:15:55,138 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled
{code}

This isn't right. For example, using {{lsof}} I can see that Wildfly bound to an ephemeral port. After starting Wildfly with {{-Djboss.management.http.port=0}}:

{code}
$ lsof -p `jps | grep jboss-modules.jar | awk '{print $1}'` -P -n | grep TCP
java    59501 jason  379u     IPv4 0xd038b817c1abd6a5       0t0      TCP 127.0.0.1:8080 (LISTEN)
java    59501 jason  387u     IPv4 0xd038b817acfc6a85       0t0      TCP 127.0.0.1:65238 (LISTEN)
java    59501 jason  390u     IPv4 0xd038b817b86956a5       0t0      TCP 127.0.0.1:8443 (LISTEN)
$ curl -v -XGET localhost:65238
Note: Unnecessary use of -X or --request, GET is already inferred.
* Rebuilt URL to: localhost:65238/
*   Trying ::1...
* TCP_NODELAY set
* Connection failed
* connect to ::1 port 65238 failed: Connection refused
*   Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to localhost (127.0.0.1) port 65238 (#0)
> GET / HTTP/1.1
> Host: localhost:65238
> User-Agent: curl/7.51.0
> Accept: */*
> 
< HTTP/1.1 301 Moved Permanently
< Connection: keep-alive
< Location: http://localhost:65238/console/index.html
< Content-Length: 0
< Date: Sun, 07 May 2017 03:25:04 GMT
< 
* Curl_http_done: called premature == 0
* Connection #0 to host localhost left intact
{code}

showing that Wildfly is indeed listening and giving the usual redirect to the Console index.

Instead, Wildfly should log the ephemeral port that it actually bound to:

{code}
23:27:09,347 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:65301/management
23:27:09,347 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:65301
{code}

  was:
When binding Wildfly Management Console to an ephemeral port (i.e., by specifying port 0), Wildfly states that the management console:

{{23:15:55,138 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0063: Http management interface is not enabled
23:15:55,138 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled}}

This isn't right. For example, using {{lsof}} I can see that Wildfly bound to an ephemeral port. After starting Wildfly with {{-Djboss.management.http.port=0}}:

{code}
$ lsof -p `jps | grep jboss-modules.jar | awk '{print $1}'` -P -n | grep TCP
java    59501 jason  379u     IPv4 0xd038b817c1abd6a5       0t0      TCP 127.0.0.1:8080 (LISTEN)
java    59501 jason  387u     IPv4 0xd038b817acfc6a85       0t0      TCP 127.0.0.1:65238 (LISTEN)
java    59501 jason  390u     IPv4 0xd038b817b86956a5       0t0      TCP 127.0.0.1:8443 (LISTEN)
$ curl -v -XGET localhost:65238
Note: Unnecessary use of -X or --request, GET is already inferred.
* Rebuilt URL to: localhost:65238/
*   Trying ::1...
* TCP_NODELAY set
* Connection failed
* connect to ::1 port 65238 failed: Connection refused
*   Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to localhost (127.0.0.1) port 65238 (#0)
> GET / HTTP/1.1
> Host: localhost:65238
> User-Agent: curl/7.51.0
> Accept: */*
> 
< HTTP/1.1 301 Moved Permanently
< Connection: keep-alive
< Location: http://localhost:65238/console/index.html
< Content-Length: 0
< Date: Sun, 07 May 2017 03:25:04 GMT
< 
* Curl_http_done: called premature == 0
* Connection #0 to host localhost left intact
{code}

showing that Wildfly is indeed listening and giving the usual redirect to the Console index.

Instead, Wildfly should log the ephemeral port that it actually bound to:

{{23:27:09,347 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:65301/management
23:27:09,347 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:65301}}



> Wildfly Management Console should log bound ports
> -------------------------------------------------
>
>                 Key: WFCORE-2771
>                 URL: https://issues.jboss.org/browse/WFCORE-2771
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Server
>            Reporter: Jason Tedor
>            Assignee: Jason Greene
>
> When binding Wildfly Management Console to an ephemeral port (i.e., by specifying port 0), Wildfly states that the management console:
> {code}
> 23:15:55,138 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0063: Http management interface is not enabled
> 23:15:55,138 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled
> {code}
> This isn't right. For example, using {{lsof}} I can see that Wildfly bound to an ephemeral port. After starting Wildfly with {{-Djboss.management.http.port=0}}:
> {code}
> $ lsof -p `jps | grep jboss-modules.jar | awk '{print $1}'` -P -n | grep TCP
> java    59501 jason  379u     IPv4 0xd038b817c1abd6a5       0t0      TCP 127.0.0.1:8080 (LISTEN)
> java    59501 jason  387u     IPv4 0xd038b817acfc6a85       0t0      TCP 127.0.0.1:65238 (LISTEN)
> java    59501 jason  390u     IPv4 0xd038b817b86956a5       0t0      TCP 127.0.0.1:8443 (LISTEN)
> $ curl -v -XGET localhost:65238
> Note: Unnecessary use of -X or --request, GET is already inferred.
> * Rebuilt URL to: localhost:65238/
> *   Trying ::1...
> * TCP_NODELAY set
> * Connection failed
> * connect to ::1 port 65238 failed: Connection refused
> *   Trying 127.0.0.1...
> * TCP_NODELAY set
> * Connected to localhost (127.0.0.1) port 65238 (#0)
> > GET / HTTP/1.1
> > Host: localhost:65238
> > User-Agent: curl/7.51.0
> > Accept: */*
> > 
> < HTTP/1.1 301 Moved Permanently
> < Connection: keep-alive
> < Location: http://localhost:65238/console/index.html
> < Content-Length: 0
> < Date: Sun, 07 May 2017 03:25:04 GMT
> < 
> * Curl_http_done: called premature == 0
> * Connection #0 to host localhost left intact
> {code}
> showing that Wildfly is indeed listening and giving the usual redirect to the Console index.
> Instead, Wildfly should log the ephemeral port that it actually bound to:
> {code}
> 23:27:09,347 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:65301/management
> 23:27:09,347 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:65301
> {code}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jboss-jira mailing list