}
    }
  }

  /**
   * Report and attempt to recover from a failure to communicate with a server. Returns true if
   * `e` is recoverable, or false if the failure is permanent. Requests with a body can only
   * be recovered if the body is buffered or if the failure occurred before the request has been
   * sent.
   */
  private fun recover(
    e: IOException,
    call: RealCall,
    userRequest: Request,

        // Assert
        assertFalse(it.hasNext());
        verify(tree, times(1)).release();
    }

    @Test
    @DisplayName("doCloseInternal throwing still releases exactly once and next() recovers")
    void closeInternalThrowsButReleases() throws Exception {
        // Arrange
        stubAcquireReturnsSelf();
        FileEntry initial = entry("first");

     * exception} and/or execute other desired logic.
     *
     * <p>Note that the method will be called even upon an invocation of {@code tryLock()}. Although
     * {@code tryLock()} technically recovers from deadlock by eventually timing out, this behavior
     * is chosen based on the assumption that it is the application's wish to prohibit any cyclical
     * lock acquisitions.
     */

        // Check if recovery is viable by testing if createTransport works
        // If createTransport returns null (no mock setup), remove immediately
        try {
            SmbTransport testTransport = manager.createTransport(failedChannel.getLocalInterface(), failedChannel.getRemoteInterface());
            if (testTransport == null) {
                // No recovery possible, remove synchronously

                log.warn("RDMA recovery attempt {} failed: {}", retryCount, recoveryError.getMessage());

                // If this was the last attempt, log the full error
                if (retryCount >= maxRetries) {
                    log.error("All RDMA recovery attempts failed", recoveryError);
                }
            }
        }

}
```

## 9. Error Handling and Fallback

### 9.1 RDMA Error Recovery
```java
public class RdmaErrorHandler {
    public void handleRdmaError(RdmaConnection connection, Exception error) {
        log.warn("RDMA error occurred: {}", error.getMessage());
        
        if (isRecoverableError(error)) {
            // Attempt to recover connection
            try {
                connection.reset();

                failoverStates.remove(channel.getChannelId());
                
                log.info("Successfully recovered channel {}", channel.getChannelId());
                
            } catch (Exception e) {
                log.warn("Failed to recover channel {}: {}", 
                    channel.getChannelId(), e.getMessage());
                
                // Schedule next retry or remove

    exception the callback is now notified that the call was canceled. The exception is still sent
    to the uncaught exception handler for reporting and recovery.

 *  Fix: Un-deprecate `MockResponse.setHeaders()` and other setters. These were deprecated in OkHttp
    4.0 but that broke method chaining for Java callers.

    URLs. (Previous releases would throw a `MalformedURLException` when calling
    a malformed URL.)

 *  **We've improved connect failure recovery.** We now differentiate between
    setup, connecting, and connected and implement appropriate recovery rules
    for each. This changes `Address` to no longer use `ConnectionSpec`. (This is
    an incompatible API change).

        
        PersistentHandleManager manager2 = new PersistentHandleManager(context);
        HandleInfo recovered = manager2.getHandleForReconnect("/test/file.txt");
        
        assertNotNull(recovered);
        assertEquals(HandleType.PERSISTENT, recovered.type);
        assertArrayEquals(fileId, recovered.fileId);
    }
}
```

### 8.2 Integration Tests
```java
@Test