Connection Leak with SP3

Question

Hi-
I recently moved from 8.1SP1 to 8.1SP3 and WOW am I getting a lot of connection leaks. I never had this problem at all with SP1 and I'm quite concerned.
My app is probably 98% CMP but I do have a bit of direct access.
My app supports both Sybase and Oracle and I get the same leak warnings with both. Other than being annoying in the console however, it doesn't seem to have any ill effects .
Here is the warning:
<Nov 8, 2004 2:35:54 PM EST> <Warning> <JDBC> <BEA-001074> <A JDBC pool connecti
on leak was detected. A connection leak occurs when a connection obtained from t
he pool was not closed explicitly by calling close() and then was disposed by th
e garbage collector and returned to the connection pool. The following stack tra
ce at create shows where the leaked connection was created. [Null exception pas
sed, creating stack trace for offending caller]
at weblogic.utils.StackTraceUtils.throwable2StackTrace(Ljava.lang.Throwable;)Ljava.lang.String;(StackTraceUtils.java:28)
at weblogic.jdbc.wrapper.JTSConnection.finalizeInternal()V(JTSConnection.java:115)
at weblogic.jdbc.wrapper.JTSConnection_com_sybase_jdbc2_jdbc_SybConnection.finalize()V(Unknown Source)
at java.lang.Object.runFinalizer()V(Unknown Source)
at java.lang.LangAccessImpl.objectFinalize(Ljava.lang.Object;)V(UnknownSource)
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)>
Any advice?
Dave

Answer 1

"David Spindle" <[email protected]> wrote in message news:17854103.1099951464437.JavaMail.root@jserv5...
I recently moved from 8.1SP1 to 8.1SP3 and WOW am I getting a lot of connection leaks. I never had this problem at all with SP1and I'm quite concerned.
>
My app is probably 98% CMP but I do have a bit of direct access.
My app supports both Sybase and Oracle and I get the same leak warnings with both. Other than being annoying in the consolehowever, it doesn't seem to have any ill effects .
>
Here is the warning:
<Nov 8, 2004 2:35:54 PM EST> <Warning> <JDBC> <BEA-001074> <A JDBC pool connecti
on leak was detected. A connection leak occurs when a connection obtained from t
he pool was not closed explicitly by calling close() and then was disposed by th
e garbage collector and returned to the connection pool. The following stack tra
ce at create shows where the leaked connection was created. [Null exception pas
sed, creating stack trace for offending caller]Null srack trace at create is a bug. Contact support for the patch.
Regards,
Slava Imeshev