Mastering Tomcat: A Deep Dive into Its Top‑Level Architecture

Tomcat Top‑Level Architecture

Tomcat’s highest‑level container is the Server , which can contain one or more Service elements. Each Service consists of a Connector (handling socket and request/response conversion) and a single Container (managing servlets).

A Server may have multiple Services; each Service may have multiple Connectors (e.g., HTTP and HTTPS) but only one Container.

The relationship is defined in server.xml, where a Server encloses Services, and each Service encloses its Connector(s) and Container.

Connector and Container Interaction

When a request arrives, the Service forwards it to its Connector, which uses a ProtocolHandler (e.g., Http11Protocol or Http11NioProtocol) to accept the socket, wrap the data into HTTP Request/Response objects, and pass them to the Container for servlet processing.

The Connector’s ProtocolHandler comprises three components: Endpoint (low‑level socket handling), Processor (HTTP request parsing), and Adapter (adapting the request to the servlet container).

Container Architecture

The Container manages servlets through four sub‑containers:

Engine : manages multiple virtual hosts.

Host : represents a virtual host (a site).

Context : corresponds to a web application (WEB‑INF directory).

Wrapper : wraps an individual servlet.

Request Processing with Pipeline‑Valve

Containers use a Pipeline‑Valve chain (a variant of the Chain of Responsibility pattern). Each container has a specific BaseValve that cannot be removed, and higher‑level containers invoke the pipelines of lower‑level containers.

The processing order is:

Connector receives the request and invokes the top‑level EnginePipeline.

EnginePipeline executes EngineValves, then calls the Host pipeline.

Host pipeline runs HostValves, then calls the Context pipeline.

Context pipeline runs ContextValves, then calls the Wrapper pipeline.

StandardWrapperValve creates a FilterChain, executes configured Filters and the target Servlet.

After all Valves finish, the response is handed back to the Connector, which sends it to the client via the socket.

Summary

Understanding Tomcat’s modular architecture—Server, Service, Connector, Container, and the Pipeline‑Valve mechanism—helps developers configure and troubleshoot the server effectively, and provides a solid foundation for interview discussions about Tomcat internals.