Server log reports wrong port for undertow listeners
Issue
- If we start JBoss with a
jboss.socket.binding.port-offset, the AJP listener port in the server log is incorrect on start up and both HTTP and AJP are incorrect on shutdown:
2017-02-14 10:21:17,251 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow AJP listener ajp listening on 127.0.0.1:8009
2017-02-14 10:21:17,251 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8180
...
2017-02-14 10:21:31,004 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow AJP listener ajp stopped, was bound to 127.0.0.1:8009
2017-02-14 10:21:31,004 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080
Environment
- JBoss Enterprise Application Platform (EAP) 7.0.5 and earlier
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.