Fix | Fix possible Statement Leak in SQLServerConnection.isValid() API

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

@@ -5568,9 +5568,8 @@ public boolean isValid(int timeout) throws SQLException {
         if (isSessionUnAvailable())
             return false;
 
-        try {
-            SQLServerStatement stmt = new SQLServerStatement(this, ResultSet.TYPE_FORWARD_ONLY,
-                    ResultSet.CONCUR_READ_ONLY, SQLServerStatementColumnEncryptionSetting.UseConnectionSetting);
+        try (SQLServerStatement stmt = new SQLServerStatement(this, ResultSet.TYPE_FORWARD_ONLY,
+                ResultSet.CONCUR_READ_ONLY, SQLServerStatementColumnEncryptionSetting.UseConnectionSetting)) {
 
             // If asked, limit the time to wait for the query to complete.
             if (0 != timeout)
@@ -5581,13 +5580,13 @@ public boolean isValid(int timeout) throws SQLException {
             // If a timeout was provided, execution throws an "query timed out" exception
             // if the query fails to execute in that time.
             stmt.executeQueryInternal("SELECT 1");
-            stmt.close();
             isValid = true;
         } catch (SQLException e) {
             // Do not propagate SQLExceptions from query execution or statement closure.
             // The connection is considered to be invalid if the statement fails to close,
             // even though query execution succeeded.
             connectionlogger.fine(toString() + " Exception checking connection validity: " + e.getMessage());
+            isValid = false;
         }
 
         loggerExternal.exiting(getClassNameLogging(), "isValid", isValid);