Uploaded image for project: 'Java Driver'
  1. Java Driver
  2. JAVA-4646

Deal with consequence of interrupted socket operation throwing SocketException

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 4.11.0
    • Affects Version/s: None
    • Component/s: Internal
    • Fully Compatible
    • 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?

      When a socket operation is interrupted (say by a call to StructuredTaskScope#joinUntil that times out, tests show that SocketInputStream#read throws a SocketException with the message "Closed by interrupt" . The driver will treat that exception according to the rules defined by the SDAM and CMAP specifications, as a network error. But it should be treated more like InterruptedException.

            Assignee:
            valentin.kovalenko@mongodb.com Valentin Kavalenka
            Reporter:
            jeff.yemin@mongodb.com Jeffrey Yemin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: