-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hikari CP Connection Recovery Problem After DB Outage #2179
Comments
We have same issue, triggered by DB outage. |
Have you tried setting the socket read timeout for Oracle JDBC? If you don't set the Read Timeout, Oracle's default socket read timeout is Refer to this and the HikariCP Rapid Recovery guide: https://github.com/brettwooldridge/HikariCP/wiki/Rapid-Recovery You can set up your configuration for HikariCP like this:
Try setting up hikariCP configruation like this. |
Context:
The following happened in a few of our test environments (but I cannot reproduce it locally).
After an outage of the DB, the connection pool was not able to recover when the DB was up and running again.
After the spring application is restarted the problem is solved, but a restart should not be necessary in this scenario.
The exception (happening over and over again until the Spring application is restarted) is:
When I reproduce the scenario locally (stopping and restarting the DB), the datasource recovers after the DB is restarted.
The problem is the same as described in https://stackoverflow.com/questions/69566390/hikari-cp-spring-boot-connection-recovery-problem-after-db-failure
The text was updated successfully, but these errors were encountered: