[jboss-jira] [JBoss JIRA] (AS7-3847) Non-standard format of IPv6 address(-es) in LOG files

[Brian Stansberry (JIRA)]

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

Brian Stansberry updated AS7-3847:
----------------------------------

    Fix Version/s: 7.1.2.Final

    
> Non-standard format of IPv6 address(-es) in LOG files
> -----------------------------------------------------
>
>                 Key: AS7-3847
>                 URL: https://issues.jboss.org/browse/AS7-3847
>             Project: Application Server 7
>          Issue Type: Bug
>    Affects Versions: 7.1.0.Final
>            Reporter: Pavel Janousek
>             Fix For: 7.1.2.Final
>
>
> There are several places where some IPv6 address related info is logged. The format of a such info is formally correct, but used format is against [RFC-5952|http://tools.ietf.org/html/rfc5952] - this RFC has status of +Proposed standard+ and I don't know any software product which doesn't follow it (at least by-default).
> I think in enterprise product we should not violate this RFC.
> I'm mentioning about LOG messages like:
> {code}
> 15:14:15,985 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /0:0:0:0:0:0:0:1%1:9999                                        
> 15:14:15,990 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on localhost6.localdomain6/0:0:0:0:0:0:0:1%1:4447                 
> {code}
> In both lines IPv6 address should be stretched to "::1" string.
> The second related issue (JBossWeb part) is tracked as AS7-3851.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira