Unable to successfully query a SQL Server 2008R2 database with JDBC

Answered Unable to successfully query a SQL Server 2008R2 database with JDBC

  • Thursday, December 06, 2012 11:32 PM
     
     

    Using the 2/17/12 SQL JDBC 4 driver we are attemping to query a 2008R2 database that is has mulitple instances and is configured with dynamic port assignment.   We are able to authenicate and create a connection to the server but when we try to call a stored procedures the JDBC driver just hangs.  We ran the profiler and it only displayed log in and log out information and nothing else. We have tried both a local SQL Server account and Integrated authenication windows account.  Both are able to log into the database but neither can call a SP.  Both hang at the same spot in the code.

    We have tried the same code against a SQL 2008R2 server with one instance and static port assignment successfully.  Has anyone ran into this before?

All Replies

  • Friday, December 07, 2012 8:03 AM
     
     

    You used the same code both in one instance server and multiple instance server?

    I think the path should be changed since using dynamic port

  • Friday, December 07, 2012 6:27 PM
     
     

    Vaphets,

    So you are asking if I used the same connect string for both servers?  You kidding right? 

    The point I am trying to make is the same Java code was run against two different server running the same version of the database and OS (SQL 2008R2 and Windows 2008R2).   I am able to execute queries and get results on the one configured with a static port.  The dynamic port connects and when I try to execute the queries it just hangs.   I see nothing in the Profiler except for the successful connection. 

    Just in case you are serious yes the two have different paths because they're different servers.  One I used the server name, instakce, and port the other I use the server and instance name and let the Brower figures out the port number for me.   The path is correct for both because they both connect. 

    Dave

  • Monday, December 10, 2012 6:09 PM
     
     Answered

    All,

    We did figure out the problem.  We were running it locally with one version of the JVM and remotely with a different one which I was unaware.  As all the blogs have mentioned JDK 6 build 29 does not work.  We upgraded to build 35 all the problems went away.

    • Marked As Answer by David Marrow Monday, December 10, 2012 6:09 PM
    •