// Cause acceptConnections() to break out.
    serverSocket.closeQuietly()

    // Await shutdown.
    for (queue in taskRunner.activeQueues()) {
      if (!queue.idleLatch().await(5, TimeUnit.SECONDS)) {
        throw AssertionError("Gave up waiting for queue to shut down")
      }
    }
    taskRunnerBackend.shutdown()
  }

  private fun serveConnection(
    connectionIndex: Int,
    raw: Socket,

        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) {

        } else if (currentChannels > targetChannels) {
            // Remove excess channels
            removeExcessChannels(currentChannels - targetChannels);
        }
    }
    
    public void shutdown() {
        scheduler.shutdown();
        
        for (ChannelInfo channel : channels.values()) {
            try {
                channel.getTransport().disconnect();
            } catch (Exception e) {

      object : okhttp3.mockwebserver.Dispatcher() {
        override fun dispatch(request: RecordedRequest): MockResponse = TODO()

        override fun peek(): MockResponse = TODO()

        override fun shutdown() = TODO()
      }
  }

  @Test
  fun dns() {
    var dns: Dns = Dns { TODO() }

    val system: Dns = Dns.SYSTEM
  }

  @Test
  fun eventListener() {
    val eventListener =

- 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...

        }
    }

    /**
     * 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()) {

### Событие `shutdown` { #shutdown-event }

Чтобы добавить функцию, которую нужно запустить при завершении работы приложения, объявите её как обработчик события `"shutdown"`:

{* ../../docs_src/events/tutorial002_py310.py hl[6] *}

Здесь функция-обработчик события `shutdown` запишет строку текста `"Application shutdown"` в файл `log.txt`.

/// info | Информация

        assertTrue(result.contains("Session Id: " + existingSessionId));
        assertEquals(existingSessionId, suggestJob.sessionId);
    }

    // Test execute method with job executor shutdown listener
    @Test
    public void test_execute_withJobExecutor() {
        createRequiredDirectories();
        MockJobExecutor mockJobExecutor = new MockJobExecutor();
        suggestJob.jobExecutor(mockJobExecutor);

### `shutdown`-Event { #shutdown-event }

Um eine Funktion hinzuzufügen, die beim Shutdown der Anwendung ausgeführt werden soll, deklarieren Sie sie mit dem Event `shutdown`:

{* ../../docs_src/events/tutorial002_py310.py hl[6] *}

Hier schreibt die `shutdown`-Eventhandler-Funktion eine Textzeile `"Application shutdown"` in eine Datei `log.txt`.

/// info | Info

在這個例子中，`startup` 事件處理器函式會用一些值來初始化 items 的「資料庫」（其實就是個 `dict`）。

你可以註冊多個事件處理函式。

而且在所有 `startup` 事件處理器都完成之前，你的應用不會開始接收請求。

### `shutdown` 事件 { #shutdown-event }

要加入一個在應用關閉時執行的函式，使用事件 `"shutdown"` 來宣告：

{* ../../docs_src/events/tutorial002_py310.py hl[6] *}

在這裡，`shutdown` 事件處理器函式會把一行文字 `"Application shutdown"` 寫入檔案 `log.txt`。

/// info

在 `open()` 函式中，`mode="a"` 表示「append（附加）」；也就是說，這行文字會加在檔案現有內容之後，而不會覆寫先前的內容。

///