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 2018/04/27 13:03:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16456356#comment-16456356 ] 

Ilya Kasnacheev commented on IGNITE-8343:
-----------------------------------------

IMO InetSocketAddress.getAddress()  should always be null-checked, via IgniteUtils method for example.

> 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: Ilya Kasnacheev
>            Priority: Major
>
> 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
(v7.6.3#76005)