You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ilya Kasnacheev (Jira)" <ji...@apache.org> on 2020/04/17 09:05:00 UTC
[jira] [Updated] (IGNITE-8343) InetSocketAddress.getAddress()
returns null, should check it in TcpCommunicationSpi
[ https://issues.apache.org/jira/browse/IGNITE-8343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ilya Kasnacheev updated IGNITE-8343:
------------------------------------
Fix Version/s: (was: 2.9)
2.8.1
> InetSocketAddress.getAddress() returns null, should check it in TcpCommunicationSpi
> -----------------------------------------------------------------------------------
>
> Key: IGNITE-8343
> URL: https://issues.apache.org/jira/browse/IGNITE-8343
> Project: Ignite
> Issue Type: Bug
> Components: general
> Reporter: Ilya Kasnacheev
> Assignee: Sergey Chugunov
> Priority: Critical
> Labels: test
> Fix For: 2.8.1
>
> Attachments: TcpDiscoveryMultiJvmTest.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This is especially notorious in the following scenario:
> {code}
> // -Djava.net.preferIPv4Stack=true
> System.err.println(new InetSocketAddress("0:0:0:0:0:0:0:1%lo", 12345).getAddress()); // null
> {code}
> Yes we already warn if different nodes have differing preferIPv4Stack, still this is warning not a error, and there may be other cases where getAddress() returns null. Should make a check.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)