ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Zhao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-2404) TcpDiscoverySpi.setLocalPortRange set 0 doesn't work
Date Fri, 11 Mar 2016 09:37:39 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190707#comment-15190707
] 

Ryan Zhao commented on IGNITE-2404:
-----------------------------------

The doc on TcpCommunicationSpi.setLocalPortRange() saying that  "If port range value is 0,
then implementation will try bind only to the port provided by setLocalPort(int) method and
fail if binding to this port did not succeed."
So, I think it would be a right choice to treat localPortRange=0 as localPortRange=1.
 I will solve it.

> TcpDiscoverySpi.setLocalPortRange set  0 doesn't work
> -----------------------------------------------------
>
>                 Key: IGNITE-2404
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2404
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Denis Magda
>              Labels: community, newbie
>
> Local port range set to 0 presently doesn't work at least for TcpCommunicationSpi and
TcpDiscoverySpi. However SPIs support it.
> In my understanding the condition has to changed to the following one (from < to <=).
> x = port; x <= port + range



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message