You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
URGENT ISSUE - Failed to create/setup connection: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "Connection reset ClientConnectionId:ebd0ff64-b053-4919-b90d-6a43ec79f25f"
#1432
Open
satscreate opened this issue
Aug 14, 2019
· 1 comment
Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64) Oct 19 2012 13:38:57 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.2 (Build 9200: )
Client Operating System
Windows 10
JAVA/JVM version
jdk1.8.0_202
Problem description
Expected behaviour:
The new connection should be enabled in the Hikari spring setup.
Actual behaviour:
Hikari pool connection dropped from max to 0 one by one at some point (it happens every two or three days once). And finally when it reaches HikariPool-1 - Pool stats (total=0, active=0, idle=0, waiting=0) then i see below exception.
Error message/stack trace:
At this time 2019-08-06 05:22:03.653 application instance killed. not sure what reason but i can see the restart script started after that time.
The text was updated successfully, but these errors were encountered:
satscreate
changed the title
Failed to create/setup connection: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "Connection reset ClientConnectionId:ebd0ff64-b053-4919-b90d-6a43ec79f25f"
URGENT ISSUE - Failed to create/setup connection: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "Connection reset ClientConnectionId:ebd0ff64-b053-4919-b90d-6a43ec79f25f"
Aug 14, 2019
Driver version
<mssql-jdbc.version>6.2.2.jre8</mssql-jdbc.version>
mssql-jdbc-6.2.2.jre8
SQL Server version
Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64) Oct 19 2012 13:38:57 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.2 (Build 9200: )
Client Operating System
Windows 10
JAVA/JVM version
jdk1.8.0_202
Problem description
Expected behaviour:
The new connection should be enabled in the Hikari spring setup.
Actual behaviour:
Hikari pool connection dropped from max to 0 one by one at some point (it happens every two or three days once). And finally when it reaches HikariPool-1 - Pool stats (total=0, active=0, idle=0, waiting=0) then i see below exception.
Error message/stack trace:
At this time 2019-08-06 05:22:03.653 application instance killed. not sure what reason but i can see the restart script started after that time.
JDBC trace logs
let me know , i can add spring TRACE log
Reproduction code
Hikari config: This issue is happening in production, as i see only this trace from the database log,
The text was updated successfully, but these errors were encountered: