Stopping the Leak: Tuning Tomcat JDBC and Executor Pools for High Concurrency
Learn how to prevent connection leaks and thread saturation in Tomcat by tuning the JDBC pool and Executor settings for high-concurrency environments.
Loading…
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to prevent connection leaks and thread saturation in Tomcat by tuning the JDBC pool and Executor settings for high-concurrency environments.
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
Designing least-privilege authentication for a JNDI JDBC resource in Tomcat 9.x and 10.x raises questions about credential lifecycle and pool behavior. JNDI resources defined in server.xml are resolved at startup, and changes typically require a restart unless the JNDI environment is reloaded via JMX. Tomcat passes the configured username and password to the