Pooled sessions should have use time updated when retrieved from the pool

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 1.3.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The session pool implementation does not update the last used time of a session, so it considers the session to be expired 30 minutes after creation, even if the session has been taken from the pool many times.

       

      User facing impact is low, as any operations that must use the same session (e.g. getMore must use the same session as the operation used to create the cursor) hold onto the session rather than putting it back in the pool.

            Assignee:
            Divjot Arora (Inactive)
            Reporter:
            Divjot Arora (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: