Uploaded image for project: 'C# Driver'
  1. C# Driver
  2. CSHARP-649

The driver should be strict about honoring MaxConnectionIdleTime and MaxConnectionLifeTime

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 1.7.1
    • 1.7
    • None
    • None

    Description

      Currently the driver is not strict about honoring the above 2 values. The connection pool maintainer removes 1 expired connection (lifetime or idle time) per maintenance run. Hence users can acquire connections from the connection pool which are either past their max idle time or max life time.
      When acquiring connections from the pool, only connections which are not past their max idle or life time should be given. Connections that are past their max idle or life time should be closed

      Attachments

        Activity

          People

            craig.wilson@mongodb.com Craig Wilson
            sridhar Sridhar Nanjundeswaran
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: