Preventing Connection Pool Exhaustion Due to Exceptional Requests & Auto-Reconnecting Druid Post Database Recovery in Spring Boot

[303470934]

**dbtype: mysql
**dbversion: 8.0.35
**druid verion: 1.2.22
error sql:
testcase code:
stacktrace info:
**error info: mysql connection error

After my project initializes successfully and begins running, both the project itself and the database operate without issue. Nonetheless, an unexpected disruption arises in which a specific data source connection to the database malfunctions, triggering a cascade of exceptions within the Spring Boot application. Amidst this anomaly, a surge of incoming requests targets this malfunctioning database connection, swiftly depleting the available resources in the connection pool. Consequently, the project grinds to a halt, leaving the Spring Boot application entirely unresponsive.

Question 1: What measures can be implemented to safeguard against excessive consumption of database connection pool resources by erroneous requests, thereby averting the suspension of project operations?
Question 2: In the event that the problematic database recovers without necessitating a restart of the Spring Boot application, what mechanisms can be employed to facilitate Druid's automatic reestablishment of connectivity with the previously troubled database service, ensuring a swift return to normal project functionality?