JTDS连接二次调用isValid()方法抛出AbstractMethodError问题求助

Hey Greg, I’ve run into this exact issue with older JTDS versions before—let’s break down what’s happening and how to fix it without needing a data source.

Why This Happens #

The java.lang.AbstractMethodError on JtdsConnection.isValid() stems from a mismatch between JDBC 4.0 specifications and older JTDS versions. Prior to JTDS 1.3.x, the driver didn’t implement the isValid(int) method introduced in JDBC 4.0. DB2’s driver natively supports this method, which is why your code works smoothly there.

Solution 1: Replace isValid() with a Custom Validation Query #

Since you’re managing connections directly (no data source involved), you can swap the isValid() check with a manual lightweight SQL query to verify connection health. Here’s how to adjust your code:

First, add a helper method to validate the connection:

private static boolean isJtdsConnectionValid(Connection conn) {
    // Use a universal query compatible with SQL Server/JTDS
    final String VALIDATION_QUERY = "SELECT 1";
    
    try (Statement stmt = conn.createStatement()) {
        stmt.executeQuery(VALIDATION_QUERY);
        return true;
    } catch (SQLException e) {
        Log.warn("JTDS connection is invalid: " + e.getMessage());
        return false;
    }
}

Then update your connection check logic to use this method instead of isValid():

case "jtds":
    Class.forName("net.sourceforge.jtds.jdbc.Driver");
    if (cJTDSConnection == null || !isJtdsConnectionValid(cJTDSConnection)) {
        Log.info("Connecting to database...");
        cJTDSConnection = getConnection(sDBUrl, sDBUser, sDBPassword);
        cJTDSConnection.setAutoCommit(false);
        Log.info("**** Connected to Database *******");
    } else {
        Log.info("No connection needed (already connected)...");
    }
    cConnection = cJTDSConnection;
    break;

This approach bypasses the unimplemented method entirely and works with all JTDS versions. The try-with-resources block ensures the Statement is closed properly to avoid resource leaks.

Solution 2: Upgrade JTDS to a JDBC 4.0-Compatible Version #

If you can update your project dependencies, upgrading to JTDS 1.3.x or newer will resolve the AbstractMethodError—these versions natively implement the isValid() method required by JDBC 4.0.

• For Maven projects, update your dependency:

  <dependency>
      <groupId>net.sourceforge.jtds</groupId>
      <artifactId>jtds</artifactId>
      <version>1.3.1</version> <!-- Use the latest stable version available -->
  </dependency>
  

• For non-Maven projects, download the latest JTDS JAR and replace your old JAR file.

Note: JTDS 1.3.x requires JDK 1.6 or higher, so confirm your project’s JDK version is compatible first.

Which Solution to Pick? #

• Custom validation query: Ideal if you can’t upgrade dependencies or need to maintain compatibility with older JDK/JTDS versions.
• Upgrade JTDS: The cleanest long-term fix, as it aligns with modern JDBC standards.

Either approach will resolve the error you’re facing. Let me know if you need help with any part of the implementation!

内容的提问来源于stack exchange，提问作者GregMa