svn commit: r1732206 - in /manifoldcf/trunk: CHANGES.txt framework/core/src/main/java/org/apache/manifoldcf/core/jdbcpool/ConnectionPool.java

[kw...@apache.org]

Author: kwright
Date: Wed Feb 24 18:56:28 2016
New Revision: 1732206

URL: http://svn.apache.org/viewvc?rev=1732206&view=rev
Log:
Fix for CONNECTORS-1281.

Modified:
    manifoldcf/trunk/CHANGES.txt
    manifoldcf/trunk/framework/core/src/main/java/org/apache/manifoldcf/core/jdbcpool/ConnectionPool.java

Modified: manifoldcf/trunk/CHANGES.txt
URL: http://svn.apache.org/viewvc/manifoldcf/trunk/CHANGES.txt?rev=1732206&r1=1732205&r2=1732206&view=diff
==============================================================================
--- manifoldcf/trunk/CHANGES.txt (original)
+++ manifoldcf/trunk/CHANGES.txt Wed Feb 24 18:56:28 2016
@@ -3,6 +3,9 @@ $Id$
 
 ======================= 2.4-dev =====================
 
+CONNECTORS-1281: SQLServer under JTDS throws AbstractMethodException.
+(Olivier Tavard, Karl Wright)
+
 CONNECTORS-1275: Help ES deal with dates properly.  Also added
 support for built-in Repository Document attributes.
 (Andrey Leybovich, Karl Wright)

Modified: manifoldcf/trunk/framework/core/src/main/java/org/apache/manifoldcf/core/jdbcpool/ConnectionPool.java
URL: http://svn.apache.org/viewvc/manifoldcf/trunk/framework/core/src/main/java/org/apache/manifoldcf/core/jdbcpool/ConnectionPool.java?rev=1732206&r1=1732205&r2=1732206&view=diff
==============================================================================
--- manifoldcf/trunk/framework/core/src/main/java/org/apache/manifoldcf/core/jdbcpool/ConnectionPool.java (original)
+++ manifoldcf/trunk/framework/core/src/main/java/org/apache/manifoldcf/core/jdbcpool/ConnectionPool.java Wed Feb 24 18:56:28 2016
@@ -96,6 +96,11 @@ public class ConnectionPool
               // Ignore this; we just can't check if handle is valid I guess.
               // (Postgresql doesn't implement this method so it fails always)
             }
+            catch (java.lang.AbstractMethodError e)
+            {
+              // Ignore this; we just can't check if handle is valid I guess.
+              // (SQLServer doesn't implement this method so it fails always)
+            }
             if (!isValid) {
               // If the connection is invalid, drop it on the floor, and get a new one.
               // Note: Order of operations is terribly important here!!