Today, we worked on a service request that our customer is using Hikaki pooler and time to time they got the following error message: HikariPool-1 - Connection ConnectionID:18 ClientConnectionId: xxxx-xxxx-xxx marked as broken because of SQLSTATE(08S01), ErrorCode(0),exc.stack=com.microsoft.sqlserver.jdbc.SQLServerException: Connection timed out (Read failed)
After reviewing several articles, for example, Improve Java application reliability with Azure SQL Database using JDBC and connection pooling. - Mi... , Using the JDBC driver - JDBC Driver for SQL Server | Microsoft Learn,
We saw that our customer is facing TCP timeouts, following a recomendation of HikariCP pooler we configure the socket timeout to 30 at least and this issue didn't happen again.
Enjoy!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.