SIMULATING CONNECTION LEAK

Question

I want to simuate Connetion LEAK
Developed a small application having only 1 JSP FILE, 1 HTML only..In JSP file
1 database connection object is used to insert a record into a database.The connection
object is not closed.. So only one connection object...
Enable VIEW LEAKING CONNECTIONS in ADMIN CONSOLE...When the appl is run , record
gets inserted sucessfully.. When the JDBC CONNECTION is right cliked to VIEW LEAKED
Connection, it does not show any message....
I have not closed the connection object. So it should show leaked connection..why
it is not displaying?????.........If this is the case, how can i check whther
a connection leak is there or not

Answer 1

Sarika Angadi wrote:
Hi,
We are using WLS6.1 SP5 and I am also getting below stack trace. This error is in production enviroment.
Could you please update me soon on this?Hi. I believe it's a false warning, having to do with internally created connection
objects in the context of sending RMI objects from server to server. You can ignore
those messages. This is already fixed in sp6 and sp7. Here is the official sp5 patch.
If you can't get it off this post, call support to get CR131575_610sp5.jar.
Joe
>
Stack Trace:
Dec 14, 2004 4:44:57 PM GMT+08:00> <Notice> <WebLogicServer> <Started WebLogic Managed Server "Managed09Dec2" for domain "gtdb10" running in Production
Mode>
[ConnectionImpl] : Detected Connection Leak!!!!! : java.lang.Throwable:
Trace at
create of ConnectionImpl
at
weblogic.jdbc.rmi.internal.ConnectionImpl.<init>(ConnectionImpl.java:
47)
at weblogic.jdbc.pool.Connection.writeReplace(Connection.java:1288)
at java.lang.reflect.Method.invoke(Native Method)
at java.io.ObjectStreamClass.invokeMethod(Unknown Source)
at java.io.ObjectOutputStream.writeObject(Unknown Source)
at
weblogic.common.internal.ChunkedObjectOutputStream.writeObject(Chunke
dObjectOutputStream.java:115)
at
weblogic.common.internal.ChunkedObjectOutputStream.writeObject(Chunke
dObjectOutputStream.java:121)
at weblogic.jdbc.common.internal.RmiDataSource_WLSkel.invoke(Unknown
Sou
rce)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:360)
at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerR
ef.java:93)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:329)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
java:22)
Thanks in advance,
Sarika[CR131575_610sp5.jar]