java.io.IOException: SQL Server did not return a response. The connection has been closed.*

osdir.com | 6 months ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    Tomcat - User - JDBC Fails to connect to SQL Server

    nabble.com | 1 year ago
    java.io.IOException: SQL Server did not return a response. The connection has been closed.*
  2. 0

    users-tomcat.apache.org - Re: JDBC Fails to connect to SQL Server - msg#00473 - Recent Discussion OSDir.com

    osdir.com | 6 months ago
    java.io.IOException: SQL Server did not return a response. The connection has been closed.*
  3. 0

    SSL Exceptions Seemingly caused by Apache Axis2

    Stack Overflow | 1 year ago | D Sass
    com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "SQL Server returned an incomplete response. The connection has been closed. ClientConnectionId:a67d09bf-be47-4910-9d8c-fd040468a1cb".
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Java 1.6 to 1.7 causes database connection to throw “The driver could not establish a secure connection to SQL Server by using SSL encryption.”

    Stack Overflow | 2 years ago | Matthew
    com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "Connection reset".
  6. 0

    db:: 4.43::Cannot create PoolableConnectionFactory da

    hivmr.com | 10 months ago
    org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: Connection reset by peer: socket write error.)

    5 unregistered visitors
    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.io.IOException

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

      at com.microsoft.sqlserver.jdbc.TDSChannel$SSLHandshakeInputStream.ensureSSLPayload()
    2. com.microsoft.sqlserver
      TDSChannel$ProxyInputStream.read
      1. com.microsoft.sqlserver.jdbc.TDSChannel$SSLHandshakeInputStream.ensureSSLPayload(IOBuffer.java:513)
      2. com.microsoft.sqlserver.jdbc.TDSChannel$SSLHandshakeInputStream.readInternal(IOBuffer.java:570)
      3. com.microsoft.sqlserver.jdbc.TDSChannel$SSLHandshakeInputStream.read(IOBuffer.java:562)
      4. com.microsoft.sqlserver.jdbc.TDSChannel$ProxyInputStream.readInternal(IOBuffer.java:757)
      5. com.microsoft.sqlserver.jdbc.TDSChannel$ProxyInputStream.read(IOBuffer.java:745)
      5 frames
    3. com.ibm.jsse2
      SSLSocketImpl.startHandshake
      1. com.ibm.jsse2.b.a(b.java:286)
      2. com.ibm.jsse2.b.a(b.java:67)
      3. com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:313)
      4. com.ibm.jsse2.SSLSocketImpl.h(SSLSocketImpl.java:63)
      5. com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:316)
      6. com.ibm.jsse2.SSLSocketImpl.startHandshake(SSLSocketImpl.java:220)
      6 frames
    4. com.microsoft.sqlserver
      TDSChannel.enableSSL
      1. com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1379)
      1 frame