How To Ensure No ResultSet/Connection/Statement Leaks Exist in Your JDBC Code
Last updated on MAY 19, 2017
Applies to:JDBC - Version 9.0.3 and later
Oracle Containers for J2EE - Version 184.108.40.206.0 to 10.1.3.5.0 [Release AS10g to AS10gR3]
Information in this document applies to any platform.
When using JDBC, it is the programmer's responsibility to ensure they release resources obtained from connections, resultsets, and statements. A popular approach is to use the DAO (Data Access Object) J2EE pattern, but by doing this the programmer must ensure they release the resources associated with using the JDBC API. This article shows how to ensure that all resources are cleanly closed in your program and gives a very simple utility for releasing resources.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms