Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-15807

In case of port is absent in IgniteClient first of all try connect on default port

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 2.11
    • 2.12
    • thin client
    • None
    • Java thin: Fixed connection logic to follow user-defined endpoint order and try the default port first.
    • Release Notes Required

    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.

      Attachments

        Issue Links

          Activity

            People

              kazakov Ilya Kazakov
              kazakov Ilya Kazakov
              Pavel Tupitsyn Pavel Tupitsyn
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 0.5h
                  0.5h