Description of problem: When https and IPv6 are used simultaneously, square brackets for IPv6 addresses are missed in some of log entries. How reproducible: Always Steps to Reproduce: 1. Config SSL (example: https://access.redhat.com/solutions/229963) 2. Config IPv6 (example: https://docs.jboss.org/author/display/AS72/Interfaces+and+ports) 3. Start EAP and check the log Actual results: ---------------------------------------- 12:05:55,396 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/0:0:0:0:0:0:0:1:8080 12:05:55,442 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) JBWEB003000: Coyote HTTP/1.1 starting on: http-/0:0:0:0:0:0:0:1:8080 ...... 12:05:55,621 INFO [org.jboss.as.remoting] (MSC service thread 1-6) JBAS017100: Listening on [::1]:4447 12:05:55,624 INFO [org.jboss.as.remoting] (MSC service thread 1-8) JBAS017100: Listening on [::1]:9999 ...... 12:05:56,328 INFO [org.jboss.as] (Controller Boot Thread) JBAS015962: Http management interface listening on https://::1:9443/management 12:05:56,330 INFO [org.jboss.as] (Controller Boot Thread) JBAS015952: Admin console listening on https://::1:9443 ---------------------------------------- Expected results: The format used for IPv6 addresses should be consistent and enclosed in square brackets Additional info: Similar bug was opened / fixed : https://bugzilla.redhat.com/show_bug.cgi?id=900564 But it appears we still got some problem when https is enabled
Upstream Jira [1] is created for those logs from Undertow: "WFLYUT0006: Undertow HTTP listener default listening on /0:0:0:0:0:0:0:1:8080" [1] - https://issues.jboss.org/browse/WFLY-5242
create bz1260566 for JBWEB log message format
bz1260566 is verified on EAP 6.4.7.CP.CR2 - IPv6 address format is now correct in CoyoteLogger in jbossweb. Square brackets are still missing in management interface and admin console log as mentioned in description.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Verified with EAP 6.4.8.CP.CR2
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.