Post reply

JDBC (jTDS) Connections reconnect after SQL 2008 R2 DB fails to another node but application generates an error

  • July 7, 2011 at 5:43 pm

    #389931

    We have JDBC (jTDS) connections to SQL Server 2008 R2 databases on Windows 2008 R2 using connection pooling. When DB fails over to another node in the cluster, the JDBC (jTDS) connections reconnect however, the application that uses those JDBC connections produces an error indicating something like "the connections to the database are in an invalid state".

    Does that indicate to some of you DBA's out there that the application is not cluster aware or that the JDBC (jTDS) driver is at fault?

    Thanks anyone who takes the time to read my email and respond.

    Patti

  • July 13, 2011 at 8:59 am

    #1352212

    I have some experience with jTDS (1.2.x) and I was left unimpressed by their Unicode support when connecting to SQL 2008 R2. Have you tried the Microsoft JDBC Driver 4.0 for SQL Server? The development team had some issues converting their error handling but it worked great. I hear they have full support for Disaster Recovery features too.

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • July 13, 2011 at 9:26 am

    #1352242

    Hey there. Glad to hear from someone regarding my post. Yes, we decided to try microsofts JDBC driver. It still didn't work for us until we put SelectMethod=cursor on the end of the URL. We just tested it today after we failed over to another node in the cluster. The JDBC connections worked perfectly. We are happy campers. 🙂

    Patti

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply