You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Thomas Vandahl (Resolved) (JIRA)" <ji...@apache.org> on 2012/04/01 18:30:28 UTC

[jira] [Resolved] (JCS-89) UDP Discovery fails to report correct IP address to peers for back-connect when InetAddress.getLocalHost() fails to return an externally-visible address (i.e. returns a local address)

     [ https://issues.apache.org/jira/browse/JCS-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Vandahl resolved JCS-89.
-------------------------------

       Resolution: Fixed
    Fix Version/s: jcs-1.4-dev

Patch applied.
                
> UDP Discovery fails to report correct IP address to peers for back-connect when InetAddress.getLocalHost() fails to return an externally-visible address (i.e. returns a local address)
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JCS-89
>                 URL: https://issues.apache.org/jira/browse/JCS-89
>             Project: Commons JCS
>          Issue Type: Bug
>            Reporter: Diego Rivera
>            Assignee: Thomas Vandahl
>             Fix For: jcs-1.4-dev
>
>         Attachments: jcs-89-fix.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> On certain environments where reverse-lookup of the machine's IP address isn't available, or other IP configurations restrict the ability of the JVM to determine its own "canonical" local address, it's impossible to determine ahead of time what address should be sent into the UDP multicast in order for lateral peers to establish the back-connection.
> The fix for this is simple: when the packet is received with the discovery message, determine the source host address of the packet that was received and set that to the discovery message's host property (setHost(packet.getAddress().getHostAddress()).  This way, it's 100% for certain we'll be back-connecting to the correct instance.
> A patch will be uploaded shortly.

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