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

Match to events ordering expected by the spec during connection closing

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Unknown Unknown
    • None
    • None
    • None
    • None

    Description

      Our current implementation doesn't generate connection closing events in an order expected by the spec.
      Spec expected order:

      1. PoolClear
      2. CheckIn
      3. ConnectionClosed;

      but the currently triggered:
      1. PoolClear
      2. ConnectionClosed
      3. CheckIn

      we should change it since it affects events asserting in test runners

      Attachments

        Activity

          People

            Unassigned Unassigned
            dmitry.lukyanov@mongodb.com Dmitry Lukyanov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: