Disable connection, but disable resultset.

If you do not use the connection pool, there is no problem. Once the connection is closed, the physical connection of the database is released, and all related Java resources can be recycled by GC.
However, if you use a connection pool, please note that the connection is not physically closed, but the connection pool is returned. Therefore, both preparedstatement and resultset are held and actually occupy the cursor resources of the relevant database, in this case, as long as the program runs for a long time, the error "the cursor exceeds the maximum allowed value of the Database" is often reported, causing the program to fail to access the database normally.

Disable connection, but disable resultset.