Why Are My Spring Boot Database Connections Dropping After Inactivity, and How Can I Prevent It?

Connection to Database Severed Beyond Set Timeframe in Spring-Boot

Connections to a database in a Spring-Boot application using JPA and Hibernate can be lost if the time between interactions exceeds a specific limit. This issue is often accompanied by an error message indicating connection issues due to the server's "wait_timeout" value being exceeded.

To address this problem, the use of Spring's testOnBorrow and validationQuery properties is discouraged. Instead, a more robust solution is to configure the following settings:

• spring.datasource.url = jdbc:mysql://localhost:3306/test?autoReconnect=true: Enable automatic reconnection in the JDBC URL.
• spring.datasource.test-while-idle=true: Test connections while they are idle.
• spring.datasource.test-on-borrow=true: Test connections before they are borrowed from the pool.
• spring.datasource.validation-query=SELECT 1: Use a validation query to check for connection validity.
• spring.datasource.time-between-eviction-runs-millis=5000: Specify the frequency of connection validation checks.
• spring.datasource.min-evictable-idle-time-millis=60000: Define the idle time limit after which connections will be checked and removed from the pool.

To prevent potential issues with active connections during transactions, it is recommended to validate connections at the beginning of a transaction and acquire a new connection if necessary.

These configuration settings will enable regular validation of connections and prevent stale connections from accumulating in the pool. As a result, the connection to the database should remain stable even for extended periods without activity.

The above is the detailed content of Why Are My Spring Boot Database Connections Dropping After Inactivity, and How Can I Prevent It?. For more information, please follow other related articles on the PHP Chinese website!