Understanding Apache Tomcat: Architecture, Components, Lifecycle, and Configuration

Apache Tomcat is an open‑source Java web application server that implements core Java EE specifications such as Servlet, JSP, JSTL, and WebSocket. It serves as the most common container for Java web applications, often used together with Spring and other libraries.

Servlet Container Structure : Tomcat consists of a Server (the whole Tomcat instance), multiple Service objects (each containing a Connector and a Container ), and the Container (Catalina) which manages the servlet lifecycle. Supporting components include Loader , Realm , JMX , Jasper (JSP engine), Pipeline with Valve s, and Naming (JNDI).

The container hierarchy further contains Engine (top‑level), Host (virtual host), Context (web‑app), and Wrapper (individual servlet).

Lifecycle Management : Tomcat defines twelve states from creation to destruction. Components implement methods like initInternal , startInternal , stopInternal , and destroyInternal . State transitions trigger events that can be listened to via listeners configured in server.xml .

Startup Process : Execution begins with start.sh , which calls Bootstrap.main . The Bootstrap loads and starts Catalina , which parses server.xml using Digester , creates the container hierarchy, and invokes StandardServer.init and start . The server then listens on the shutdown port (default 8005) to terminate gracefully.

Connector Types : Tomcat supports three connector implementations—BIO (blocking I/O), NIO (non‑blocking I/O with selector‑based multiplexing), and APR (native I/O via Apache Portable Runtime). Each can be selected in server.xml and has different performance characteristics regarding polling, thread usage, and I/O handling.

NIO Processing : An Acceptor thread accepts connections and creates PollerEvent s. Poller threads retrieve events, use a Selector to detect readable sockets, and dispatch Http11NioProcessor instances to a thread pool. The CoyoteAdapter bridges the connector to the container pipeline.

Comet Support : Tomcat implements server‑push via the Comet API. A servlet that implements CometProcessor receives callbacks such as begin , read , end , and error to manage long‑lived connections.

Asynchronous Servlet : Since Servlet 3.0, Tomcat allows asynchronous processing. A request can call request.startAsync() , releasing the servlet thread while keeping the response open. The async thread later completes the response via the saved AsyncContext . Lifecycle events onStartAsync , onComplete , onError , and onTimeout can be listened to.

Code Example – Parallel Container Startup :

List<Future<Void>> results = new ArrayList<Future<Void>>();
for (int i = 0; i < children.length; i++) {
    results.add(startStopExecutor.submit(new StartChild(children[i]));
}
boolean fail = false;
for (Future<Void> result : results) {
    try {
        result.get();
    } catch (Exception e) {
        log.error(sm.getString("containerBase.threadedStartFailed"), e);
        fail = true;
    }
}

The article also includes practical notes on configuring server.xml for hosts, contexts, and connectors, as well as explanations of JSP lifecycle, JSP elements, and the role of valves in the pipeline.