Hibernate version:2.1.8

Name and version of the database you are using:oracle 10g

Weblogic 8.1 SP3

I am seeing some pool connection leak error from Weblogic log. Would it be cause by non-closed hibernate session? Or collection object not being iterated?

Our customer is not reporting any issue using the site but I am afraid it might be a issue.

<Warning> <JDBC> <BEA-001074> <A JDBC pool connection leak was detected. A connection leak occurs when a connection obtained from the pool was not closed explicitly by calling close() and then was disposed by the garbage collector and returned to the connection pool. The following stack trace at create shows where the leaked connection was created. [Null exception passed, creating stack trace for offending caller]
< at weblogic.utils.StackTraceUtils.throwable2StackTrace(Ljava.lang.Throwable;)Ljava.lang.String;(StackTraceUtils.java:28)
< at weblogic.jdbc.wrapper.PoolConnection.finalizeInternal()V(PoolConnection.java:84)
< at weblogic.jdbc.wrapper.PoolConnection_oracle_jdbc_driver_T4CConnection.finalize()V(Unknown Source)
< at java.lang.Object.runFinalizer()V(Unknown Source)
< at java.lang.LangAccessImpl.objectFinalize(Ljava.lang.Object;)V(Unknown Source)
< at java.lang.ref.Finalizer.runFinalizer()V(Unknown Source)
< at java.lang.ref.Finalizer.access$100(Ljava.lang.ref.Finalizer;)V(Unknown Source)
< at java.lang.ref.Finalizer$FinalizerThread.run()V(Unknown Source)
< at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
<>

If your using JTA (CMT) using the containers DB resource then its reasonably hard to create a leak. Its unlikely its a general problem with your code since the pool would be exhaused very quickly. This is hard to find without some form of tracing going on. Most Pool managers can deal with the occational leaked connection anyway - most liklely there is an system exception being generated thats not being caught hence the cause.

Thanks for your reply but I am not seeing any exception being thrown. We captured and output the stack trace in our code but none of them were showed up. I have been running the same piece of code under different Weblogic platform (7), but not seeing the same exception. Is there a way from Hibernate to trace down the issue?