Uploaded image for project: 'Java Driver'
  1. Java Driver
  2. JAVA-4216

DefaultConnectionPool and ConcurrentPool incorrectly handle some maxSize values

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.4.0
    • Component/s: Connection Management
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Documentation Changes:
      Not Needed

      Description

      • If maxSize is 0, then
        • DefaultConnectionPool.createTimeoutException works incorrectly because it considers the value to be 0 instead of being infinite;
        • ConcurrentPool is created with 0 semaphore permits and does not allow creating connections.
      • If maxSize is negative, then
        • ConcurrentPool creates a semaphore with negative permits, which means connections must be released before they can be created. The ConcurrentPool docs state "if < 0 then no limit".

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              valentin.kovalenko Valentin Kavalenka
              Reporter:
              valentin.kovalenko Valentin Kavalenka
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: