Uploaded image for project: 'Java DCP Client'
  1. Java DCP Client
  2. JDCP-137

Increase connection name limit from 148 bytes to 200 bytes

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Fixed
    • Major
    • 0.25.0
    • None
    • None
    • 1

    Description

      The previous limit of 148 bytes was a conservative guess. With the resolution of MB-34280 we now know the actual safe limit is 200 bytes.

      As a result, the user agent string can be truncated less aggressively, and will include more information about the JVM and other platform details.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JDCP-126 Rebalance fails because DCP connection name is too long

          • Major - Major loss of function.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. MB-34280 Memcached should disallow DCP connections with names greater than 200 characters (was: ns_server connections may be terminated if a client uses a long DCP_OPEN.name)

          • Major - Major loss of function.
          • Closed
          For Gerrit Dashboard: JDCP-137
          # Subject Branch Project Status CR V
          119330,2 JDCP-137 Increase connection name limit from 148 bytes to 200 bytes master java-dcp-client Status: MERGED +2 +1

          Activity

            People

              david.nault David Nault
              david.nault David Nault
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty