Pre-write context expiration should not be considered a network error

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 1.10.2
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Benji Rewis (Inactive)
              Reporter:
              Divjot Arora (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: