[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-1229) Display recreated InvokerLocator when bind address is 0.0.0.0

[Ron Sigal (JIRA)]

    [ https://jira.jboss.org/browse/JBREM-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12535840#action_12535840 ] 

Ron Sigal commented on JBREM-1229:
----------------------------------

JBREM-1180 "Formally reject hostnames which don't conform to RFC-952" addresses the same issue, so JBREM-1229 is just added protection.


> Display recreated InvokerLocator when bind address is 0.0.0.0
> -------------------------------------------------------------
>
>                 Key: JBREM-1229
>                 URL: https://jira.jboss.org/browse/JBREM-1229
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.3.SP2, 2.5.2.SP3 (Flounder)
>            Reporter: Ron Sigal
>            Assignee: Ron Sigal
>            Priority: Minor
>             Fix For: 2.2.3.SP3, 2.5.2.SP4 (Flounder) 
>
>
> Occasionally, the character "_" is used in hostnames, which is illegal, according to http://www.ietf.org/rfc/rfc952.txt.  The java.net.URI parser gets confused, and the detectable  phenomenon is the replacement of the port with -1.  
> When 0.0.0.0 is given as the bind address, org.jboss.remoting.ServerInvoker calls org.jboss.Remoting.InvokerLocator.validateLocator() to create an InvokerLocator with a host accessible over a network.  By default, the host name is used, which leads to the problem described above.
> If the system property InvokerLocator.BIND_BY_HOST (actual value "remoting.bind_by_host"), the host address will be used instead, which would work around the problem.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira