- Checks if a ResultSet is closed twice
- Checks if a ResultSet is not closed at all (in the finalizer)
- Checks if a ResultSet yields unread columns
In addition to static code analysis tools like FindBugs or Alvor, this tool can help you find very subtle memory leaks in your large legacy application. Certainly a tool to have on your tool chain!
import com.maginatics.jdbclint.ConnectionProxy; ... Connection connection = DriverManager.getConnection(...); connection = ConnectionProxy.newInstance( connection, new Properties()); connection.close(); // reports error and optionally throws exception connection.close();
One thought on “Detect JDBC API Misusage with JDBCLint”
Thanks for the hint, usefool tool.