[ https://issues.apache.org/jira/browse/KUDU-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17207979#comment-17207979 ]
Alex Dettinger edited comment on KUDU-3200 at 10/22/20, 7:39 AM: ----------------------------------------------------------------- Maybe a solution could be to change the implementation of org.apache.kudu.client.HostAndPort so that it returns only host and port to maintain pre-jdk 12 behavior. was (Author: aldettinger): May a solution could be to change the implementation of org.apache.kudu.client.HostAndPort so that it returns only host and port. > 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 > > 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)