Enabling HTTP/2 on Tomcat 10: A Practical Step‑by‑Step Guide
Configure Tomcat 10 for HTTP/2 by adding an NIO2 HTTPS connector with ALPN support, validate with curl and DevTools, and recover by reverting to the backup if necessary.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Configure Tomcat 10 for HTTP/2 by adding an NIO2 HTTPS connector with ALPN support, validate with curl and DevTools, and recover by reverting to the backup if necessary.
Learn how to tune the Tomcat Executor to prevent CPU exhaustion and connection refusals. This guide covers maxThreads, acceptCount, and the risks of thread starvation.
Clients hit Tomcat 400 Bad Request when request headers exceed the connector’s maxHttpHeaderSize. This guide walks through symptoms, diagnostics, configuration changes, verification, and escalation steps to resolve the issue on Tomcat 9/10.
Learn how to tune Tomcat's NIO connector by balancing maxThreads, maxConnections, and acceptCount to prevent connection refusals and CPU thrashing in high-traffic apps.
Learn how Tomcat’s NIO connector reduces thread overhead for high‑concurrency apps, with a concrete config example, monitoring tips, and trade‑off analysis.
Goal Create a repeatable development environment for a Java web application that guarantees consistent behavior across team members and CI pipelines. Constraint Classpath isolation is critical: the application must run without interference from external libraries or frameworks that may be present on the host JVM. Unresolved Decision Both the Embedded Tomcat
After running DDL (for example, adding a column) against a database fronted by a Tomcat JDBC Pool, existing pooled connections can become stale. The pool offers two documented validation strategies: testOnBorrow with a validationQuery , which checks each connection when it is borrowed and discards it on failure, and testWhileIdle with the periodic eviction r
We run Tomcat on both Linux and Windows hosts and want to pick a single connector strategy for a high-traffic HTTP endpoint. The documentation describes NIO as the portable pure-Java default, while APR/native can use platform-native pollers and OpenSSL-style TLS integration but requires matching native libraries per OS and packaging. Our constraint is maximi