assertThat(server.takeRequest().exchangeIndex).isEqualTo(1) // New connection.
  }

  /**
   * We had a bug where we'd perform infinite retries of route that fail with connection shutdown
   * errors. The problem was that the logic that decided whether to reuse a route didn't track
   * certain HTTP/2 errors. https://github.com/square/okhttp/issues/5547
   */
  @Test

            }
            httpClient = null;
            if (clientConnectionManager != null) {
                clientConnectionManager.shutdown();
                if (logger.isDebugEnabled()) {
                    logger.debug("HTTP client connection manager shutdown complete");
                }
            }
        }
    }

    /**
     * Adds a property to the HTTP client configuration.
     *

## Version 3.4.2

_2016-11-03_

 *  Fix: Recover gracefully when an HTTP/2 connection is shutdown. We had a
    bug where shutdown HTTP/2 connections were considered usable. This caused
    infinite loops when calls attempted to recover.


## Version 3.4.1

_2016-07-10_

 *  **Fix a major bug in encoding HTTP headers.** In 3.4.0 and 3.4.0-RC1 OkHttp

        try {
            // Cancel rotation task
            if (rotationTask != null) {
                rotationTask.cancel(false);
                rotationTask = null;
            }

            // Shutdown rotation scheduler
            rotationScheduler.shutdownNow();

            clearAllKeys();
        } finally {
            // Wipe KeyStore password
            if (keyStorePassword != null) {

  @BeforeEach
  fun setUp() {
    platform.assumeNotOpenJSSE()
    platform.assumeHttp2Support()
  }

  @AfterEach
  fun tearDown() {
    executorService.shutdown()
  }

  @Test
  @Throws(IOException::class)
  fun http1DoesntSupportDuplex() {
    val call =
      client.newCall(
        Request
          .Builder()
          .url(server.url("/"))

     */
    public void close() {
        if (thresholdAdjustmentTask != null) {
            thresholdAdjustmentTask.cancel(false);
        }
        if (scheduler != null) {
            scheduler.shutdown();
        }
        log.info("[{}] Circuit breaker closed and resources cleaned up", name);
    }

    private void startDynamicThresholdAdjustment() {

        }
    }

    /**
     * Destroys the DI container and stops the timeout manager.
     * This method ensures proper cleanup of resources when the crawler shuts down.
     * It's called both during normal shutdown and in error conditions.
     */
    private static void destroyContainer() {
        if (running.getAndSet(false)) {
            TimeoutManager.getInstance().stop();
            if (logger.isDebugEnabled()) {

     * </ul>
     *
     * <p>The method includes error handling, retry logic, and will terminate
     * if too many empty results are encountered or if a system shutdown is requested.
     */
    @Override
    public void run() {
        if (dataService == null) {

    } catch (uhe: UnknownHostException) {
      throw TestAbortedException(uhe.message, uhe)
    }
  }

  fun OkHttpClient.close() {
    dispatcher.executorService.shutdown()
    connectionPool.evictAll()
  }

- Reverts graceful node shutdown to match 1.21 behavior of setting pods that have not yet successfully completed to "Failed" phase if the GracefulNodeShutdown feature is enabled in kubelet. The GracefulNodeShutdown feature is beta and must be explicitly configured via kubelet config to be enabled in 1.21+. This changes 1.22 and 1.23 behavior on node shutdown to match 1.21. If you do not want pods to be marked terminated on node shutdown in...