ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Dropwizard services rely on JDBC connection pools. This guide compares HikariCP, Apache DBCP, and C3P0, explains trade‑offs, and shows a concrete HikariCP configuration with validation steps.
A decision guide for picking a JDBC connection pool in Tomcat: comparing the built-in Tomcat JDBC Pool, HikariCP, and DBCP2 with concrete JNDI configurations and validation steps.
When using Spring Data JPA's Pageable interface in a JHipster-generated service, each pagination request triggers two SQL statements: a data query with LIMIT/OFFSET and a separate count query to determine the total number of rows. Under concurrent load, the count query can occupy a connection for the duration of its execution, especially on large tables lack
Goal: Enable developers to view JDBC connection‑pool health directly inside a Vaadin Flow application without relying on external monitoring tools. Constraint: Vaadin Flow does not create or manage its own pool; it delegates to the container or Spring Boot’s HikariCP‑based DataSource, and the framework currently offers no dedicated API or UI component to sur
Goal I want to configure Dynatrace metric events so my team is warned about intermittent connection pool exhaustion in our Java services before requests start failing, rather than after. OneAgent already reports pool usage for our HikariCP pools, and PurePath shows which requests hold connections. Constraints and uncertainty Alerting on absolute saturation (
Bitbucket Server utilizes HikariCP for JDBC connection pooling, with a default maximum-pool-size of 10. The pool manages connection lifecycles through background eviction and idle timeouts to ensure resource efficiency. A potential conflict arises when the database server's own idle timeout is configured to be shorter than the application's eviction interval
Connection Pool Exhaustion Under Peak Load Spring Boot applications using HikariCP can experience intermittent connection pool exhaustion during peak traffic periods. The default maximumPoolSize of 10 connections may be insufficient when concurrent requests spike, causing the pool to deplete faster than connections are returned. During load testing, the appl
Goal: Diagnose intermittent HikariCP connection pool exhaustion and determine if the pool can be configured to automatically reclaim connections that exceed the leakDetectionThreshold without manual intervention. Constraint: HikariCP logs leaked connections when they surpass leakDetectionThreshold but does not evict them; the pool waits for the application t
Connection Pool Exhaustion in JHipster Applications JHipster-generated Spring Boot applications rely on HikariCP for database connection pooling. Under high concurrency, the application may encounter a ConnectionTimeoutException when the number of active request threads exceeds the configured maximum-pool-size , causing threads to block until the connection-
dropwizard
tomcat
jhipster
vaadin
dynatrace
bitbucket
npss