A container is running as long as the **main process** (command or program) is running.

A container normally has a **single process**, but it's also possible to start subprocesses from the main process, and that way you will have **multiple processes** in the same container.

But it's not possible to have a running container without **at least one running process**. If the main process stops, the container stops.

        assertEquals("processed: template with params", result);
    }

    // Test evaluate with empty parameters
    public void test_evaluate_emptyParams() {
        Map<String, Object> emptyParams = new HashMap<>();
        Object result = testScriptEngine.evaluate("template", emptyParams);
        assertEquals("processed: template with params", result);
    }

        return systemHelper.getRedirectResponseToRoot(newHtmlResponseAsRedirect("/"));
    }

    /**
     * Processes the given path through the virtual host helper to handle
     * virtual host configurations and path modifications.
     *
     * @param path the HTML path to process
     * @return the processed path with virtual host handling applied
     */
    protected HtmlNext virtualHost(final HtmlNext path) {

Mas tenha em mente que, como tudo é manipulado na memória, em uma única lista, ele só funcionará enquanto o processo estiver em execução e só funcionará com um único processo.

import org.opensearch.search.aggregations.bucket.terms.Terms;

import com.google.common.io.BaseEncoding;

/**
 * Response object for faceted search results containing query counts and field facets.
 * This class processes OpenSearch aggregations to provide structured facet information
 * for search result filtering and navigation.
 */
public class FacetResponse {
    /**

        }
        return urlSet;
    }

    /**
     * Processes the response data from a crawled URL, including failure handling.
     * This method extends the base response processing to handle Fess-specific failure
     * URL tracking when certain HTTP status codes are encountered.
     *
     * @param urlQueue the URL queue item that was processed
     * @param responseData the response data from the crawl operation
     */

        }

        /**
         * Sets whether plugins should be processed during project building.
         * When true, the builder will process plugin information which may include
         * resolving plugin dependencies and executing plugin goals that participate in project building.
         *
         * @param processPlugins true if plugins should be processed, false otherwise
         * @return this builder instance
         */

      sink.flush()
    }
  }

  /**
   * Tell the peer to stop creating streams and that we last processed `lastGoodStreamId`, or zero
   * if no streams were processed.
   *
   * @param lastGoodStreamId the last stream ID processed, or zero if no streams were processed.
   * @param errorCode reason for closing the connection.
   * @param debugData only valid for HTTP/2; opaque debug data to send.
   */

        } catch (JobProcessingException e) {
            assertTrue(e.getMessage().contains("10 crawler processes are running"));
            assertTrue(e.getMessage().contains("Max processes are 5"));
        }
    }

    // Test execute method with no max process limit
    public void test_execute_noMaxProcessLimit() {
        // Setup test
        crawlJob = new CrawlJob() {

```

</div>

////

La única opción nueva aquí es `--workers` indicando a Uvicorn que inicie 4 worker processes.

También puedes ver que muestra el **PID** de cada proceso, `27365` para el proceso padre (este es el **gestor de procesos**) y uno para cada worker process: `27368`, `27369`, `27370`, y `27367`.

## Conceptos de Despliegue