java.io.IOException

SQL Server did not return a response. The connection has been closed.*

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web24400

  • SQL Server did not return a response. The connection has been closed.*
  • via nabble.com by Unknown author, 1 year ago
    SQL Server did not return a response. The connection has been closed.*
  • SQL Server did not return a response. The connection has been closed. ClientConnectionId:aae3c3a9-9b39-4141-aeda-577e06a28dfd
  • Stack trace

    • java.io.IOException: SQL Server did not return a response. The connection has been closed.* at com.microsoft.sqlserver.jdbc.TDSChannel$SSLHandshakeInputStream.ensureSSLPayload(IOBuffer.java:513) at com.microsoft.sqlserver.jdbc.TDSChannel$SSLHandshakeInputStream.readInternal(IOBuffer.java:570) at com.microsoft.sqlserver.jdbc.TDSChannel$SSLHandshakeInputStream.read(IOBuffer.java:562) at com.microsoft.sqlserver.jdbc.TDSChannel$ProxyInputStream.readInternal(IOBuffer.java:757) at com.microsoft.sqlserver.jdbc.TDSChannel$ProxyInputStream.read(IOBuffer.java:745) at com.ibm.jsse2.b.a(b.java:286) at com.ibm.jsse2.b.a(b.java:67) at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:313) at com.ibm.jsse2.SSLSocketImpl.h(SSLSocketImpl.java:63) at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:316) at com.ibm.jsse2.SSLSocketImpl.startHandshake(SSLSocketImpl.java:220) at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1379)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 1 year ago
    8 times, 1 month ago
    Unknown user
    Once, 11 months ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    1 more bugmates