Understanding Tomcat’s Startup Process: From Bootstrap to Lifecycle

Tomcat Startup Process

Starting Tomcat involves executing the startup script (bin/startup.bat or bin/startup.sh), which calls catalina.bat, then invokes the main method of the BootStrap class.

The BootStrap main method calls init to create a Catalina instance and initialize the class loader, then calls load, which in turn calls Catalina.load.

During Catalina.load, initialization tasks are performed, including constructing a Digester object to parse XML configuration files.

Subsequent steps load Tomcat’s configuration, initialize container components, set up listeners, and prepare to accept client requests.

Key Interfaces and Lifecycle

Tomcat abstracts component lifecycle management through the Lifecycle interface. Core components such as Server, Service, Container, Executor, and Connector implement this interface, providing the methods:

init() – initialize component

start() – start component

stop() – stop component

destroy() – destroy component

Default Implementations

Interfaces like Server, Service, Engine, Host, and Context have default implementation classes. For network endpoints, Tomcat defines an abstract AbstractEndpoint with three concrete subclasses: NioEndpoint, Nio2Endpoint, and AprEndpoint. Tomcat 8.5 uses NioEndpoint by default.

Protocol Handlers

Protocol handling is performed by ProtocolHandler implementations, which wrap an Endpoint and a Processor. Tomcat provides six implementations for AJP and HTTP protocols, each supporting different I/O models (NIO, NIO2, APR).

Source Entry Point

Directory: org.apache.catalina.startup
MainClass: BootStrap --> main(String[] args)

Summary

The startup sequence follows a standardized lifecycle: init() is called to initialize components hierarchically, followed by start() to launch them. Each component not only performs its own processing but also invokes the lifecycle methods of its child components, allowing loose coupling and easy reconfiguration via configuration files.