You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Grant Henke (Jira)" <ji...@apache.org> on 2020/10/22 16:37:00 UTC

[jira] [Resolved] (KUDU-3200) KuduTestHarness is not working from JDK 12 onward

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

Grant Henke resolved KUDU-3200.
-------------------------------
    Fix Version/s: 1.14.0
       Resolution: Fixed

This issue was fixed by [https://github.com/apache/kudu/commit/41a7c4e4e8165ec42312afa919550f815b3e808d]

 

> KuduTestHarness is not working from JDK 12 onward
> -------------------------------------------------
>
>                 Key: KUDU-3200
>                 URL: https://issues.apache.org/jira/browse/KUDU-3200
>             Project: Kudu
>          Issue Type: Test
>            Reporter: Alex Dettinger
>            Assignee: Grant Henke
>            Priority: Major
>             Fix For: 1.14.0
>
>
> From JDK12 onward, the KuduTestHarness seems not to be functional anymore.
> After investigation, the log below gives a good indication:
> {code:java}
> ERROR NetUtil - Failed to resolve the IP of `127.11.24.188/<unresolved>'{code}
> And looking deeper, it could be traced down to:
> {code:java}
> MiniKuduCluster.getMasterAddressesAsString()
> ...
> HostAndPort.toString()
> ...
> InetSocketAddress.toString()
> {code}
> which behavior has changed in JDK 12.
> Prior to JDK12, values like 192.168.24.44:14444 would be returned.
> From JDK 12 onward, values like 192.168.24.44*/<unresolved>*:14444 are expected in this case.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)