A Java web application needs a server that can receive requests and run its web components. Apache Tomcat supplies that runtime for applications built against the supported Servlet and related web specifications. Teams use it to host compatible applications without building the request-handling infrastructure themselves. The application’s Java version and API generation determine the appropriate Tomcat branch; crossing the older Java EE to Jakarta package-name boundary may require application and dependency changes rather than only a newer container image.
Current guidance
Apache’s current version matrix maps supported Tomcat branches to Java and specification levels and separately lists retired branches. Select a supported combination for the application instead of treating the highest image tag as a compatible replacement for the historical chart’s runtime.
A major migration boundary is the change from javax-based specification packages to jakarta-based packages in Tomcat 10 and later. Apache documents recompilation and a migration tool, but application libraries, filters and framework versions still need compatibility review. The historical 9-to-10 guide explains that boundary; it is not a recommendation to deploy the now-superseded Tomcat 10.0 branch.
Build and test the WAR against the chosen runtime, checking authentication, sessions, uploads, character encoding and database connections. Preserve configuration and any externalized application data separately from container images. In Kubernetes, design readiness and graceful shutdown around in-flight requests, and decide how sessions survive rescheduling. Avoid exposing management applications unnecessarily. A successful server startup does not prove that all deployed applications or custom Tomcat components are compatible.
Historical upstream link check · 2026-10-09
The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Original publication: 2018-09-20T07:21:05+00:00. Preserved for context. Commands, versions, prices and results below reflect the original research.
The Apache Tomcat® software is an open source implementation of the Java Servlet, JavaServer Pages, Java Expression Language, and Java WebSocket technologies. The Java Servlet, JavaServer Pages, Java Expression Language, and Java WebSocket specifications are developed under the Java Community Process.
The Apache Tomcat software is developed in an open and participatory environment and released under the Apache License version 2. The Apache Tomcat project is intended to be a collaboration of the best-of-breed developers from around the world. We invite you to participate in this open development project. To learn more about getting involved, click here.
Apache Tomcat software powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations. Some of these users and their stories are listed on the PoweredBy wiki page.
Apache Tomcat, Tomcat, Apache, the Apache feather, and the Apache Tomcat project logo are trademarks of the Apache Software Foundation.
Components
Tomcat 4.x was released with Catalina (a servlet container), Coyote (an HTTP connector) and Jasper (a JSP engine).
Catalina
Catalina is Tomcat’s servlet container. Catalina implements Sun Microsystems’s specifications for servlet and JavaServer Pages (JSP). In Tomcat, a Realm element represents a “database” of usernames, passwords, and roles (similar to Unix groups) assigned to those users. Different implementations of Realm allow Catalina to be integrated into environments where such authentication information is already being created and maintained, and then use that information to implement Container Managed Security as described in the Servlet Specification.
Coyote
Coyote is a Connector component for Tomcat that supports the HTTP 1.1 protocol as a web server. This allows Catalina, nominally a Java Servlet or JSP container, to also act as a plain web server that serves local files as HTTP documents.
Coyote listens for incoming connections to the server on a specific TCP port and forwards the request to the Tomcat Engine to process the request and send back a response to the requesting client. Another Coyote Connector, Coyote JK, listens similarly but instead forwards its requests to another web server, such as Apache, using the JK protocol.[5] This usually offers better performance.[citation needed]
Jasper
Jasper is Tomcat’s JSP Engine. Jasper parses JSP files to compile them into Java code as servlets (that can be handled by Catalina). At runtime, Jasper detects changes to JSP files and recompiles them.
As of version 5, Tomcat uses Jasper 2, which is an implementation of the Sun Microsystems’s JSP 2.0 specification. From Jasper to Jasper 2, important features were added:
- JSP Tag library pooling – Each tag markup in JSP file is handled by a tag handler class. Tag handler class objects can be pooled and reused in the whole JSP servlet.
- Background JSP compilation – While recompiling modified JSP Java code, the older version is still available for server requests. The older JSP servlet is deleted once the new JSP servlet has finished being recompiled.
- Recompile JSP when included page changes – Pages can be inserted and included into a JSP at runtime. The JSP will not only be recompiled with JSP file changes but also with included page changes.
- JDT Java compiler – Jasper 2 can use the Eclipse JDT (Java Development Tools) Java compiler instead of Ant and javac.
Three new components were added with the release of Tomcat 7:
Cluster
This component has been added to manage large applications. It is used for load balancing that can be achieved through many techniques. Clustering support currently requires the JDK version 1.5 or higher.
High availability
A high-availability feature has been added to facilitate the scheduling of system upgrades (e.g. new releases, change requests) without affecting the live environment. This is done by dispatching live traffic requests to a temporary server on a different port while the main server is upgraded to the main port. It is very useful in handling user requests on high-traffic web applications.
Web application
It has also added the user- as well as system-based web applications enhancement to add support for deployment across the variety of environments. It also tries to manage sessions as well as applications across the network.
Tomcat is building additional components. A number of additional components may be used with Apache Tomcat. These components may be built by users should they need them or they can be downloaded from one of the mirrors.
Features
Tomcat 7.x implements the Servlet 3.0 and JSP 2.2 specifications.It requires Java version 1.6, although previous versions have run on Java 1.1 through 1.5. Versions 5 through 6 saw improvements in garbage collection, JSP parsing, performance, and scalability. Native wrappers, known as “Tomcat Native”, are available for Microsoft Windows and Unix for platform integration.
Tomcat 8.x implements the Servlet 3.1 and JSP 2.4 Specifications. Apache Tomcat 8.5.x is intended to replace 8.0.x and includes new features pulled forward from Tomcat 9.0.x. The minimum Java version and implemented specification versions remain unchanged.
Communities
Apache software is built as part of a community process that involves both user and developer mailing lists. The developer list is where discussion on building and testing the next release takes place, while the user list is where users can discuss their problems with the developers and other users.
Some of the free Apache Tomcat resources and communities include Tomcatexpert.com (a SpringSource sponsored community for developers and operators who are running Apache Tomcat in large-scale production environments) and MuleSoft’s Apache Tomcat Resource Center (which has instructional guides on installing, updating, configuring, monitoring, troubleshooting and securing various versions of Tomcat).
The post Tomcat appeared first on kubedex.com.
Sources & further reading
Spotted something that needs another look?
Help improve this page →