Details
-
Task
-
Resolution: Unresolved
-
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