DriverManagerConnectionPoolConnection not closed, check your code!

Question

DriverManagerConnectionPoolConnection not closed, check your code!
I keep getting these, both from custom jdbc calls (finally {close res, stmt, con} ALWAYS) as well as on CMP entity beans.... Not always, but periodicly! ... Running OC4J9.0.4.0.1 ...
Suggestions ???

Answer 1

Sorry Steven Button
I did not mean to offend any one, but don't you go through some frustrating moments when you feel you have tried all possible combinations and u need help from other techies and they do not respond, Once again I am sorry if I have offended anybody.
Here is my hardware/software in production
1) IBM AIX
2) Standalone OC4J 9.0.4.0.0
3) JDK 1.4.2_07
4) Database 10.1.0.2.0
I have also set the following debug flags for the JVM,
-Djdbc.connection.debug=true and
-Ddatasource.verbose=true
Yesterday one interesting thing happened
For some reason our database server connection from application server went down for a few minutes.
After the network connection was restored, in the admin console for OC4J I see more logical connections (Open JDBC Connections count(6) is more than initial pool size(5)).
When I saw the log file I see the same "Check your code" message. But one more interesting thing got logged thanks to "-Ddatasource.verbose=true", this flag will log the pool size of the connection pool in the application log file.
The number that got logged was the correct number of pool size(which is 5).
Example
My initial pool size was "5", the admin console showed the pool size after network failure as "6", which is wrong.
But the -Ddatasource.verbose=true logged the pool size as "5" which is correct.
Can anyone help me with respect to that?
Message for Avi Abrami
Here is the sample finally block we use through out the application code.
try {
} catch (Exception ex) {
// we log the error in the application log file.
} finally {
try
if (lobj_resultset != null)
lobj_resultset.close();
lobj_resultset = null;
} catch (Exception exrs)
try
if (lobj_stmt != null)
lobj_stmt.close();
lobj_stmt = null;
} catch (Exception exstmt)
try
if (lobj_conn != null)
lobj_conn.close();
lobj_conn = null;
} catch (Exception exconn)
As you can see the main catch block will log the appropriate errors encountered in the try block. Thanks for your suggestion, I will give it a try by not ignoring the catch block exceptions in the finally block.
There is one more think,
it is my understanding that if an 'Error' is raised like OutOfMemoryError rather than an Exception
like 'SQLException' then that will not get caught since I am using catch (Exception ex) and not catch (Throwable throw).
But even if I do not catch an 'Error', it is my belief that the finally block will still get executed.
So say the try block for some reason raises an OutOfMemoryError , since in my code I use catch (Exception ex), my code execution will go to finally block and not the catch block, that still should release the connection back to the pool should it not?.
Any help / advise is appreciated.
I have also raised a TAR with oracle and will keep this forum posted with what happens with that.
But, guys I really need help, suggestions, directions from u all.