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

Fri Feb 24 10:00:37 EST 2012

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

Pavel Janousek updated AS7-3847:
--------------------------------

    Description: 
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.

  was:
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.

More "funny" and obfuscated version of the same LOG content is LOG line like this:
{code}
15:14:14,363 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Starting Coyote HTTP/1.1 on http--0%3A0%3A0%3A0%3A0%3A0%3A0%3A1%251-8080
{code}

But both version of the issue is almost unreadable by human.

> 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
>
> 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