Uploaded image for project: 'Couchbase .NET client library'
  1. Couchbase .NET client library
  2. NCBC-1417

Error when creating bucket "The port number must be greater than 1023..."

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.1.0, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2.0, 2.2.1, 2.2.2, 2.2.3, 2.2.4, 2.2.5, 2.2.6, 2.2.7, 2.2.8, 2.3.0, 2.3.1, 2.3.2, 2.3.4, 2.3.5, 2.3.6, 2.3.7, 2.3.8, 2.3.9, 2.3.10, 2.4.0, 2.4.1, 2.3.11, 2.4.2, 2.4.3, 2.4.4
    • Fix Version/s: 2.4.5
    • Component/s: library
    • Labels:
      None
    • Environment:
      Windows, Enterprise Edition 5.0.0-2564

      Description

      Summary: Error message "The port number must be greater than 1023..." when trying to create a bucket.

      Repro:

      1. Install Enterprise Edition 5.0.0-2565
      2. Create .NET console app (I used .NET Core and CouchbaseNetClient 
      3. Connect to cluster and create cluster manager using Admin credentials (see below)
      4. Try to create a bucket with clusterManager.CreateBucket(...)

      Expected:

      Bucket to be created (or at least a more actionable error message than "The port number must be greater than 1023...")

      Actual:

      Success = false, Message = "The port number must be greater than 1023...".

      Bucket does not get created.

      Code:

      var cluster = new Cluster(new ClientConfiguration
      {{ {}}
      {{ Servers = new List<Uri> { new Uri("http://localhost:8091")},}}
      {{ UseSsl = false}}
      {{ });}}

      var clusterManager = cluster.CreateManager("Administrator", "password"); 

      {{ var resp = clusterManager.CreateBucket("testbucket", replicaNumber: 0);}}

        Attachments

          Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            Activity

            Hide
            mike.goldsmith Michael Goldsmith added a comment -

            Fix in NCBC-1345

            Show
            mike.goldsmith Michael Goldsmith added a comment - Fix in NCBC-1345
            Hide
            mike.goldsmith Michael Goldsmith added a comment -

            Release notes for 2.4.4 has been updated to indicate this is an existing bug for all 2.X clients.

            Show
            mike.goldsmith Michael Goldsmith added a comment - Release notes for 2.4.4 has been updated to indicate this is an existing bug for all 2.X clients.
            Hide
            dfinlay Dave Finlay added a comment -

            Thanks guys.

            Show
            dfinlay Dave Finlay added a comment - Thanks guys.
            Hide
            btburnett3 Brant Burnett added a comment -

            Michael Goldsmith

            This issue is marked as resolved in 2.4.5, but I noticed that on the website it's still listed as a known issue for 2.4.5 and 2.4.6.

            https://developer.couchbase.com/server/other-products/release-notes-archives/dotnet-sdk

            Brant

            Show
            btburnett3 Brant Burnett added a comment - Michael Goldsmith This issue is marked as resolved in 2.4.5, but I noticed that on the website it's still listed as a known issue for 2.4.5 and 2.4.6. https://developer.couchbase.com/server/other-products/release-notes-archives/dotnet-sdk Brant
            Hide
            mike.goldsmith Michael Goldsmith added a comment -

            Hi Brant Burnett

            The issue was fixed as part of NCBC-1345 which only set the proxyPort property if it's different from the default. The server changed behaviour where it used to ignore invalid values where it now rejects the request.

            We set this as a known issue on past versions if they were to be used on server 5.0+. If you use a later version you won't see the same behaviour.

            Show
            mike.goldsmith Michael Goldsmith added a comment - Hi Brant Burnett The issue was fixed as part of NCBC-1345 which only set the proxyPort property if it's different from the default. The server changed behaviour where it used to ignore invalid values where it now rejects the request. We set this as a known issue on past versions if they were to be used on server 5.0+. If you use a later version you won't see the same behaviour.

              People

              • Assignee:
                mike.goldsmith Michael Goldsmith
                Reporter:
                matthew.groves Matthew Groves
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Gerrit Reviews

                  There are no open Gerrit changes

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.