[IGNITE-15807] In case of port is absent in IgniteClient first of all try connect on default port

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.11
• Fix Version/s: 2.12
• Component/s: thin client
• Release Note: Java thin: Fixed connection logic to follow user-defined endpoint order and try the default port first.
• Ignite Flags: Release Notes Required
• Assignee: Ilya Kazakov
• Reporter: Ilya Kazakov
• Reviewer: Pavel Tupitsyn
• Created: 25/Oct/21 04:11
• Updated: 25/Jan/23 13:40
• Resolved: 10/Nov/21 04:30

Description

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.

Issue Links

• causes: IGNITE-18637 Java thin client: Connections balancing
• links to: GitHub Pull Request #9522