Improve maxCommitTime timeout error message

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Error Handling
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Customer claim, in the Java driver, or probably other drivers, the error message clients get is not clear in the following scenario.

      1. When maxCommitTime is set, if a transaction timed out because of writeconcern not met the error message is:

      Caused by: com.mongodb.MongoExecutionTimeoutException: operation exceeded time limit
      

      2. When the maxCommitTime is set, but the transaction timed out for commit issues other than writeconcern not met, the error is the same.

      Caused by: com.mongodb.MongoExecutionTimeoutException: operation exceeded time limit
      

      Can we make this distinguishable? There're cases where customers wants to retry a transaction in scenario 2, but not 1.

              Assignee:
              Jeffrey Yemin
              Reporter:
              Jennifer Huang (Inactive)
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: