Hi Tom,

In the https://asktom.oracle.com/pls/apex/asktom.search?tag=jdbc-thin-dirver-vs-oci-driver question you stated that one should only use the OCI driver if some OCI-specific features are required.

However, as stated in https://www.thatjeffsmith.com/archive/2013/04/die-or-how-to-cancel-queries-in-oracle-sql-developer/ there is also a huge difference between the Thin and OCI Driver when it comes to the Query Timeout handling.

When I use a Query-Timeout on a select statement that requires a full table scan on a huge table like this

        try (Connection con = dataSource.getConnection(); 
                Statement statement = con.createStatement()) {
            statement.setQueryTimeout(10);  // 10 seconds

            try (ResultSet rs = statement.executeQuery(
                    "select * " +
                    "from my_huge_table " + 
                    "where column_without_index = 'some Value'")) {
             
                 // do something with the result set 

            }
        }

the JDBC driver sends in both cases a "Statement.cancel()" request after the defined timeout. However, when I use the JDBC-Thin driver, the cancel Request has no effect and my statements keeps on running for many more minutes until it produces the requested result set. On the contrary when using the JDBC-OCI driver, I immediately get the expected "java.sql.SQLTimeoutException: ORA-01013" Exception.

Is there any way to configure the Thin driver that it handles cancellation requests as reliable as the OCI driver?