Hi Chris,

One of our customer reported a similar issue and the issue can be resolved
through the bug fix 8169865 which was include at 8u152 level. We were
looking this issue from AIX perspective as it did not do the reverse lookup
with bug fix 8169865 (as reverse lookup is limited to solaris after the bug

While implementing the fix, we want to make sure the fix works for all
scenario. As there is an inconsistency between IPv6 and IPv4 after 8169865
(as reverse lookup still exists for IPv4 on AIX and Linux), we are afraid
whether customer can hit the same issue if they use IPv4.

Please confirm whether it makes sense to remove the reverse lookup of IPv4
for AIX and linux platforms so that IPv4 and IPv6 processing is consistent
for those platforms.

Srividya S

From:   Chris Hegarty <chris.hega...@oracle.com>
To:     Srividya Shamaiah <ssham...@in.ibm.com>,
Date:   09/04/2018 09:41 PM
Subject:        Re: 8169865 : Changes not ported to IPv4

Hi Srividya,

On 09/04/18 10:58, Srividya Shamaiah wrote:
> Hi ,
> In method Java_java_net_Inet6AddressImpl_getLocalHostName , file
> *src/solaris/native/java/net/Inet6AddressImpl.c *, there were changes
> that was added due to *8169865: Downport minor fixes in java.net native
> code from JDK 9 to JDK 8 *which removed the additional work for non
> Solaris platforms of doing a reverse lookup to get the hostname. Is
> there any specific reason as to why the same change is not added to
> method Java_java_net_Inet4AddressImpl_getLocalHostName, file
> *src/solaris/native/java/net/Inet4AddressImpl.c *. For IPv4 we still
> continue to resolve hostname through nameservice for all UNIX platforms
> while for IPv6 we do this only for Solaris platforms.

The changes for 8169865, in this area, were mainly motivated
by clean up, rather than function. I agree that there is an
inconsistency between the IPv4 and IPv6 lookup
implementations. This inconsistency has been for many many
years. Are you seeing any specific issues relating to this?


Reply via email to