Match to events ordering expected by the spec during connection closing

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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

            Assignee:
            Unassigned
            Reporter:
            Dmitry Lukyanov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: