Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
Description
The connection#writeWireMessage function does an optimistic check for context expiration and returns an error without writing to the socket because it knows the write will fail anyway. This is a good idea, but the error is considered a network timeout by the operations layer, which is incorrect. We should either remove this check altogether or move it into the Operation#Execute function and not call WriteWireMessage at all if the context is expired.
Attachments
Issue Links
- is related to
-
GODRIVER-2065 Error early if insufficient time remains for socket operation
-
- Closed
-
- related to
-
GODRIVER-2468 Don't check Context expiration in WithTransaction
-
- Closed
-