This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
Okay. I know this error happens when we don't close the connections / statements / resultsets properly. But, is there a way to find out which connection / statement / resultset is left open? This is a huge application and it is next to impossible to do a code review and find out where the mistake lies. Is it possible somehow to know which connection / statement / resultset is creating the problem? (either by monitoring at the Oracle end or using some logging in Java front?)
Thanks. The cursor size is set to 1000 in Oracle -more than enough for this application. And, it is currently not possible to make any big changes to this application. So the DAO approach is ruled out, at least for now.