Unify Timeout Exception Checks

XMLWordPrintableJSON

    • None
    • Java Drivers
    • Not Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      Description: Currently, there is an inconsistency in how timeout-related exceptions are handled in our codebase. Specifically, the method hasExpired is checked in
      throwTranslatedWriteException, while hasTimeoutMS is checked the translateReadException method. This discrepancy was noted during a review where it was observed that we should not check for onExpired when a MongoSocketWriteTimeoutException is caught. If a timeout exception from the socket occurs and timeoutMS is enabled, it indicates that a CSOT (Client-Side Operation Timeout) has occurred.
      This ticket aims to unify the logic across these methods to ensure consistent handling of timeout exceptions.

              Assignee:
              Slav Babanin
              Reporter:
              Slav Babanin
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: