ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
The goal is to determine whether the New Relic Java agent records the exact moment a HikariCP connection pool reaches its maximum size, or only reports aggregated connection counts at each harvest window. The agent collects pool metrics on a default 60‑second harvest cycle, and Java agent 8.x renamed the metric namespace from Database/ConnectionPool/* to Dat
Configuration Goal JHipster generates Spring Boot applications using HikariCP as the default connection pool implementation. The generator's application.yml template includes hikari configuration, but the exact logic for calculating maximumPoolSize may not be fully transparent to developers deploying to production environments. Relevant Constraints The defau
Dropwizard's DataSourceFactory uses HikariCP by default, and the documented behavior when the pool is exhausted is that callers wait up to connectionTimeout before a SQLTransientConnectionException is thrown. With connectionTimeout set to zero, waiting threads block indefinitely, which risks starving the Jetty worker pool under sustained load. The unresolved
Goal Diagnose intermittent connection pool exhaustion when NetBeans Database Explorer interacts with databases or application servers that enforce connection limits. Constraints and uncertainty The Data Sources UI exposes only URL, username, password, and driver class. HikariCP pool properties such as maximum pool size, idle timeout, minimum idle connections
Grails 4 and later default to HikariCP for GORM data sources, so low-traffic cost tuning is configured through dataSource.properties.* keys in application.yml rather than legacy Tomcat pool settings. The goal is to reduce database connection or session costs for a workload that sits idle for extended periods. HikariCP interprets minimumIdle as a floor and ma
When a long‑running DML statement is terminated with KILL QUERY , MySQL aborts the statement but leaves the surrounding transaction open. The storage engine may still be rolling back row changes, which determines when locks are actually released. Meanwhile, a Java connection pool such as HikariCP typically validates a borrowed connection with a lightweight q
Connection Pool Configuration in Elastic Environments JHipster leverages HikariCP as the default connection pool provider, integrating closely with Spring Boot's externalized configuration. In highly elastic cloud environments, the application must balance rapid scaling of container instances against the fixed connection limits of the underlying database. Cu
External Pool Dependency in Hibernate 6.2 Hibernate 6.2 has removed its built-in connection pool, shifting the responsibility of connection management entirely to external providers such as HikariCP or C3P0. In environments utilizing Spring Boot 3.0, HikariCP is provided by default, but its default configuration may not align with the concurrency requirement
newrelic
jhipster
dropwizard
hibernate