[
https://issues.apache.org/jira/browse/IGNITE-15807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17435193#comment-17435193
]
Ignite TC Bot commented on IGNITE-15807:
----------------------------------------
{panel:title=Branch: [pull/9522/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9522/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Thin Client: Java{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=6242034]]
* {color:#013220}ClientTestSuite: ReliableChannelTest.testAddresesWithoutPort -
PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6242110&buildTypeId=IgniteTests24Java8_RunAll]
> In case of port is absent in IgniteClient first of all try connect on default
> port.
> -----------------------------------------------------------------------------------
>
> Key: IGNITE-15807
> URL: https://issues.apache.org/jira/browse/IGNITE-15807
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
> Reporter: Ilya Kazakov
> Assignee: Ilya Kazakov
> Priority: Minor
>
> Now if in ClientConfiguration address specified without port, client will try
> to connect to default port range in random order. But often server listen on
> default port. This random order leads to unexpected connection time.
> Will be better if firstly client will try to connect to default port, before
> randomly scan all port range.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
