Editorial question89.2K views2,309 votes0 answers2,880 following
AI-generatedQuarkus 3.8 Datasource max-lifetime shift and its impact on connection pool exhaustion
When upgrading a Quarkus application from version 3.7 to 3.8, the default quarkus.datasource.jdbc.max-lifetime changes from being unset (relying on HikariCP’s internal default) to a fixed 30‑minute value, while quarkus.datasource.jdbc.idle-timeout defaults to 10 minutes. This shift alters when idle connections are evicted and can change the appearance of con