[
https://issues.apache.org/jira/browse/IGNITE-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15191072#comment-15191072
]
ASF GitHub Bot commented on IGNITE-2404:
----------------------------------------
GitHub user ryanzz opened a pull request:
https://github.com/apache/ignite/pull/549
IGNITE-2404
For TcpDiscoverySpi and TcpCommunicationSpi, 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.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ryanzz/ignite ignite-2404
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/549.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #549
----
commit 7c6d33a49f8005d5dc66f10044efe8cfea9ad8be
Author: Ryan Zhao <[email protected]>
Date: 2016-03-11T14:54:41Z
fixed ignite-2404
----
> 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
> Assignee: Ryan Zhao
> 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)
