Question

I’m trying to write a really simple GUI app for inserting some records
into a database, and reading back some records (nothing fancy, just 1 table with 3 rows, no relations).
The source…

package EntryProg;
import java.sql.*;
import com.microsoft.sqlserver.jdbc.*;



public class CourseDataEntryHandler
{
    private Connection connect;
    private CallableStatement callState;
    private ResultSet rSet;
    private SQLServerDataSource dSource;

    public CourseDataEntryHandler()
    {
        rSet = null;
        callState = null;

        dSource = new SQLServerDataSource();
        dSource.setUser(REDACTED);
        dSource.setPassword(REDACTED);
        dSource.setServerName(REDACTED);
        dSource.setPortNumber(REDACTED);
        dSource.setDatabaseName(REDACTED);
        dSource.setEncrypt(true);
        dSource.setTrustServerCertificate(true);
        try
        {

Error here

            connect = dSource.getConnection();

end error

        }
        catch (SQLServerException e)
        {
            //TODO Figure out how to handle -- logging for now, console
            do
            {
                System.out.println(e.getErrorCode());
                System.out.println(e.getMessage());
                System.out.println(e.getSQLState());
                e = (SQLServerException) e.getNextException();
            } while (e != null);
            System.out.println("END");
            System.out.println();
        }
    }

I get the following error…

(code)0

(message)SQL Server did not return a response. The connection has been closed.

(state)08S01

I’ve verified that the user,pass,server name,port, and DB name are all accurate.
If I change the username to a non-valid one, I get a “could not log in” error reported back so I know I’m hitting the server.

I’ve not been able to fully connect once, so I know it’s not a “too many connections” issue, as the only person currently logged into the server is me via sql management studio. It doesn’t work when I log out of that either so definitely not a connections # issue.

The applications user has datareader/datawriter permissions as well.
(I’m using Eclipse, if that matters. And am referencing the sqljdbc4.jar library).

I’m at a loss as to where to go with troubleshooting this. Any help would be greatly appreciated.

EDIT
Update – I’ve also tried a connection string and using DriverManager.getConnection(connString) to set the connection, that didn’t work either. The result is the same.
Also, SQL server 2008 r2 is the sql server version I’m using.

EDIT
I wrote a quick C# program to test the connection, sure enough the connection works fine in .net, unfortunately I have to use java for this project (it’s a project I’ve chosen to do on my own for a class, only requirement is it be in Java…teacher has no clue what’s going on either).

Answer 1

Comment the line with setEncrypt(true):

...
dSource.setDatabaseName(REDACTED);
//dSource.setEncrypt(true);
dSource.setTrustServerCertificate(true);
...

You might have trouble with the encryption setting. From the setEncrypt(…) documentation:

If the encrypt property is set to true, the Microsoft SQL Server JDBC Driver uses the JVM’s default JSSE security provider to negotiate SSL encryption with SQL Server. The default security provider may not support all of the features required to negotiate SSL encryption successfully. For example, the default security provider may not support the size of the RSA public key used in the SQL Server SSL certificate. In this case, the default security provider might raise an error that will cause the JDBC driver to terminate the connection. In order to resolve this issue, do one of the following:

• Configure the SQL Server with a server certificate that has a smaller RSA public key

• Configure the JVM to use a different JSSE security provider in the “/lib/security/java.security” security properties file

• Use a different JVM

Update

With Java versions 1.6.0_29 and 7.0.0_1 Oracle introduced a security fix for the SSL/TLS BEAST attack that very likely will cause the very same problem. The above security fix is known to make trouble for database connections to MSSQL Server with both the jTDS driver and the Microsoft driver. You can either

• decide not to use encryption by not using setEncrypt(true) (as specified above)
• or, if it is enforced by MSSQL Server, you could turn off the Java fix in your JVM by setting the -Djsse.enableCBCProtection=false system property. Be warned, it will affect all SSL connections within the same VM.