The Tomcat startup process begins with org.apache.catalina.startup.Bootstrap#main, which serves as the JVM entry point. This method orchestrates classloader initialization, component wiring, and lifecycle orchestration based on command-line arguments.

String operation = extractOperation(args);

switch (operation) {
    case "start":
        instance.configureAwaitMode(true);
        instance.loadConfiguration(args);
        instance.launchServer();
        if (instance.getServer() == null) System.exit(1);
        break;
    case "stop":
        instance.shutdownServer(args);
        break;
    case "configtest":
        instance.loadConfiguration(args);
        System.exit(instance.getServer() != null ? 0 : 1);
        break;
    case "startd":
        args[args.length - 1] = "start";
        instance.loadConfiguration(args);
        instance.launchServer();
        break;
    case "stopd":
        args[args.length - 1] = "stop";
        instance.shutdownServer(args);
        break;
    default:
        log.warn("Unsupported operation: " + operation);
}

}

</div>The `Catalina` class implements the core container lifecycle. Its `load()` method bootstraps infrastructure including:

- Temporary directory setup via `initDirs()`
- JNDI naming environment initialization
- XML configuration parsing using Apache Commons Digester to instantiate the `StandardServer` hierarchy from `conf/server.xml`
- System stream redirection through `SystemLogHandler` for thread-safe console output
- Invocation of `server.init()` — triggering recursive initialization of nested components like `StandardEngine`, thread pools (`Executor`), `Connector`s, and `MapperListener`

<div class="code-block">```
public void loadConfiguration(String[] args) {
    initDirs();
    initNaming();

    Digester parser = buildConfigurationParser();
    parser.push(this);

    try (InputStream configStream = locateServerXml()) {
        InputSource source = new InputSource(configStream);
        parser.parse(source);
    } catch (Exception e) {
        log.error("Failed to parse server configuration", e);
        throw new IllegalStateException(e);
    }

    Server server = getServer();
    server.setCatalina(this);
    server.setCatalinaHome(Bootstrap.getCatalinaHomeFile());
    server.setCatalinaBase(Bootstrap.getCatalinaBaseFile());

    initStreams();

    try {
        server.initialize(); // Triggers init() on all nested Lifecycle components
    } catch (LifecycleException e) {
        if (shouldExitOnInitFailure()) throw new Error(e);
        log.error("Server initialization failed", e);
    }
}

The start() method activates the entire component tree:

• Invokes server.start(), propagating start signals to Engine, Connectors, and associated thread pools
• When await mode is enabled, it launches a blocking ServerSocket on the shutdown port (default: 8005)
• This socket listens for the exact string "SHUTDOWN"; upon receipt, it triggers graceful termination via server.stop()

if (isAwaitEnabled()) {
    try {
        getServer().await(); // Blocks until SHUTDOWN command received
    } catch (InterruptedException e) {
        Thread.currentThread().interrupt();
    }
    stopServer();
}

}

</div>The shutdown mechanism relies on inter-process communication: `shutdown.bat/sh` launches a separate JVM that connects to the running server’s shutodwn socket and transmits the termination command.