Fine-Tuning Tomcat 8 JDBC Connection Pool

Search for a command to run...

No comments yet. Be the first to comment.
Somewhere in your organisation right now, a dashboard is showing a healthy deployment frequency, a stable change failure rate, and a throughput line that ticks gently upward. Leadership is satisfied.

Every organization with procedure-driven back-office operations faces the same invisible problem: knowledge lives in three disconnected silos โ training videos, static documents, and SME expertise โ w

Part 2 of 2 | DataOps Labs Series: Living Knowledge Systems on AWS

You've tuned your embedding model. You've benchmarked retrieval algorithms. You've swapped LLMs. And your RAG system still gets the wrong answer. Here's what nobody tells you upfront: the bottleneck i

Reasoning and Orchestration (OpenClaw) - Runtime (AWS AgentCore) - Scalable DataLayer (Elastic)

maxActiveDescription: Maximum number of active connections in the pool.
๐ Issue: Too low = connection starvation. Too high = DB overload.
maxActive="100"
๐ Tomcat 8 Docs - maxActive
maxWaitDescription: How long (in ms) to wait for a connection before throwing an exception.
๐ Issue: Low value = frequent timeouts under load.
maxWait="10000"
validationQuery, testOnBorrow, and validationIntervalDescription: Checks that a DB connection is valid before returning it to the app.
๐ Issue: Stale connections lead to failed transactions.
testOnBorrow="true"
validationQuery="SELECT 1"
validationInterval="30000"
๐ Tomcat 8 Docs - validationQuery & testOnBorrow
minIdle, maxIdle, timeBetweenEvictionRunsMillis, minEvictableIdleTimeMillisDescription: Controls idle connection cleanup to avoid leaks and unnecessary DB usage.
minIdle="10"
maxIdle="30"
timeBetweenEvictionRunsMillis="30000"
minEvictableIdleTimeMillis="60000"
๐ Tomcat 8 Docs - Idle Connection Settings