Directly call invalidateEnclaveSessionCache from reconnect

Author: machavan

src/main/java/com/microsoft/sqlserver/jdbc/SQLServerConnection.java

@@ -2193,14 +2193,7 @@ Connection connect(Properties propsIn, SQLServerPooledConnection pooledConnectio
         // Any existing enclave session would be invalid, make sure it is invalidated.
         // For example, if this is a session recovery reconnect.
         //
-
-        if (enclaveProvider != null) {
-            if (connectionlogger.isLoggable(Level.FINE)) {
-                connectionlogger.fine("Invalidating existing enclave session for enclave provider : " + enclaveProvider);
-            }
-            enclaveProvider.invalidateEnclaveSession();
-        }
-
+        invalidateEnclaveSessionCache();
         for (int connectRetryAttempt = 0, tlsRetryAttempt = 0;;) {
             try {
                 if (0 == elapsedSeconds || elapsedSeconds < loginTimeoutSeconds) {

src/main/java/com/microsoft/sqlserver/jdbc/SQLServerException.java

@@ -89,7 +89,7 @@ public final class SQLServerException extends java.sql.SQLException {
     static final int DATA_CLASSIFICATION_NOT_EXPECTED = 11;
     static final int DATA_CLASSIFICATION_INVALID_LABEL_INDEX = 12;
     static final int DATA_CLASSIFICATION_INVALID_INFORMATION_TYPE_INDEX = 13;
-    
+
     static final java.util.logging.Logger exLogger = java.util.logging.Logger
             .getLogger("com.microsoft.sqlserver.jdbc.internals.SQLServerException");