Fix potential connection leak when using jdbc storage and Scan operation fails because the target table doesn't exist

core/src/main/java/com/scalar/db/storage/jdbc/JdbcDatabase.java

@@ -105,7 +105,7 @@ public Scanner scan(Scan scan) throws ExecutionException {
       connection.setAutoCommit(false);
       rdbEngine.setConnectionToReadOnly(connection, true);
       return jdbcService.getScanner(scan, connection);
-    } catch (SQLException e) {
+    } catch (Exception e) {
       try {
         if (connection != null) {
           connection.rollback();

core/src/test/java/com/scalar/db/storage/jdbc/JdbcDatabaseTest.java

@@ -138,6 +138,29 @@ public void whenScanOperationExecutedAndScannerClosed_shouldCallJdbcService() th
     verify(connection).close();
   }
 
+  @Test
+  public void
+      whenScanOperationExecutedAndJdbcServiceThrowsIllegalArgumentException_shouldThrowExecutionException()
+          throws Exception {
+    // Arrange
+    Exception cause = new IllegalArgumentException("Table not found");
+    // Simulate the table not found scenario.
+    when(jdbcService.getScanner(any(), any())).thenThrow(cause);
+
+    // Act Assert
+    assertThatThrownBy(
+            () -> {
+              Scan scan = new Scan(new Key("p1", "val")).forNamespace(NAMESPACE).forTable(TABLE);
+              jdbcDatabase.scan(scan);
+            })
+        .isInstanceOf(ExecutionException.class)
+        .hasCause(cause);
+    verify(connection).setAutoCommit(false);
+    verify(connection).setReadOnly(true);
+    verify(connection).rollback();
+    verify(connection).close();
+  }
+
   @Test
   public void
       whenScanOperationExecutedAndScannerClosed_SQLExceptionThrownByConnectionCommit_shouldThrowIOException()