Guest Jose_Manuel_Jurado Posted January 27, 2023 Posted January 27, 2023 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. - Microsoft Community Hub , 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! Continue reading... Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.