[DRIVERS-688] Add "connectionError" as a valid "reason" for a ConnectionCheckOutFailedEvent when connection set up fails Created: 04/Jul/19  Updated: 28/Oct/23  Resolved: 09/Jan/20

Status: Closed
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Shane Harvey Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on CSHARP-2664 Add "connectionError" as a valid "rea... Closed
depends on NODE-2049 Add "connectionError" as a valid "rea... Closed
depends on PYTHON-1900 Add "connectionError" as a valid "rea... Closed
depends on RUBY-1874 Add "connectionError" as a valid "rea... Closed
is depended on by DRIVERS-538 Implement Connection Monitoring and P... Closed
Related
related to DRIVERS-538 Implement Connection Monitoring and P... Closed
related to JAVA-3348 Add "connectionError" as a valid "rea... Closed
Driver Compliance:
Key Status/Resolution FixVersion
PYTHON-1900 Fixed 3.9
NODE-2049 Fixed 3.5.0
CSHARP-2664 Duplicate
PERL-1119 Won't Fix
RUBY-1874 Fixed 2.11.0.rc0
SWIFT-544 Done

 Description   

Spec changes here: https://github.com/mongodb/specifications/commit/ef782f2be3bfa32cb3c2befb63d85de142df31aa

Changes:

  • Add "connectionError" as a valid reason for ConnectionCheckOutFailedEvent
  • Add a prose test for ConnectionCheckOutFailedEvent(reason="connectionError")
  • Add a spec test for ConnectionCheckOutFailedEvent(reason="poolClosed")

Generated at Thu Feb 08 08:22:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.