Stack Trace for Connection leak

Anthony Hong

unread,

Jul 7, 2004, 11:33:37 PM7/7/04

to

I saw a message that bea has debug patch for trace each connection connection,
leak ....
I met such problem and I'm interested in this debug path.
Can you send this patch for me?
My wls version is 8.1sp2

Joe Weinstein

unread,

Jul 8, 2004, 10:33:50 AM7/8/04

to Anthony Hong

Anthony Hong wrote:

Hi. Have you tried enabling leak profiling? Do you have any symptoms of
pool leaks?
Joe

Anthony Hong

unread,

Jul 8, 2004, 11:33:23 AM7/8/04

to

Yes, After I run some functions. I saw there were some information given by weblogic
said it detect a connection not closed.
But it's hard for me to check all codes. So I want some tools to have such traceability.

And I found it in your newsgroup that one person has such requirement for his
weblogic server 7.0.

Anthony Hong

unread,

Jul 8, 2004, 9:05:23 PM7/8/04

to

I have following information given by weblogic server

I think my program have connection leak, Am I right?

Anthony Hong

unread,

Jul 12, 2004, 9:44:26 AM7/12/04

to

Thanks Joe, It works fine.
I found the connection leak.
By the way, I have one more question about it.
Each weblogic server version has its correspond connection leak debug lib?
When I want to find problem in future version. I have to ask for this lib again?

Joe Weinstein <joeN...@bea.com> wrote:
>
>
>
>Anthony Hong wrote:
>
>> I have following information given by weblogic server
>>
>> <Jul 6, 2004 10:48:33 PM CST> <Warning> <Common> <BEA-000620> <Forcibly
>releasing
>> inactive resource "weblogic.jdbc.common.internal.ConnectionEnv@152b696"
>back into
>> the pool "jdbcpool".>
>> <Jul 6, 2004 10:48:48 PM CST> <Warning> <Common> <BEA-000631> <Unknown
>resource
>> "weblogic.jdbc.common.internal.ConnectionEnv@152b696" being released
>to pool "jdbcpool".
>> Printing out current pool contents.>
>>
>> I think my program have connection leak, Am I right?
>

>Maybe. Please take the attached debug jar, and get it listed ahead of
>the weblogic.jar
>in the classpath created by the start script for the server. Then run
>as usual, and
>when that message is printed out, it should include a trace of where
>the connection
>was reserved. That way you can identify what code got a connection and
>didn't close it.
>Note though, that in 81sp2, the code that reclaims idle connections doesn't
>actually
>know if the connection is really idle or whether it is really waiting
>for a long time
>for a DBMS call to return...
>Joe

Joe Weinstein

unread,

Jul 12, 2004, 1:55:14 PM7/12/04

to Anthony Hong

Anthony Hong wrote:

> Thanks Joe, It works fine.
> I found the connection leak.
> By the way, I have one more question about it.
> Each weblogic server version has its correspond connection leak debug lib?
> When I want to find problem in future version. I have to ask for this lib again?

Glad to help. If the pool is configured for Leak Profiling you should get this behavior.

n lo

unread,

Aug 18, 2004, 11:57:44 AM8/18/04

to

Hi Joe,

Could you please send us the [81sp2conenv_pool.jar]

We are experiencing the same problem with our app under wls12 sp2 with oracle thin driver.

Regards,
nlo

Joe Weinstein

unread,

Aug 18, 2004, 12:32:36 PM8/18/04

to

n lo wrote:

WLS12?
Joe

n lo

unread,

Aug 18, 2004, 3:42:40 PM8/18/04

to

Oops, wls81

n lo

unread,

Aug 18, 2004, 5:33:28 PM8/18/04

to

Is the 81sp2conenv_pool.jar file downloadable from BEA (if yes, please advise the URI) or should I expect to receive it as an attachment ?

Regards,
nlo

Joe Weinstein

unread,

Aug 18, 2004, 5:41:48 PM8/18/04

to

n lo wrote:

I attached it in my last newsgroup post. It is a debug jar of my own creation.
If you email me, I can resend it directly.
Joe

j
o
e
AT
b
e
a
DOT
c
o
m

tester tester

unread,

Aug 24, 2004, 3:59:42 PM8/24/04

to

Hi Joe,

I am also getting the following stacktrace with WLS81SP3. I am not sure how to find the actual connection leak. Is you debug jar helpful for Sp3 too?

<Aug 24, 2004 6:23:59 PM GMT> <Warning> <JDBC> <BEA-001074> <A JDBC pool connect
ion 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 t
he garbage collector and returned to the connection pool. The following stack tr
ace at create shows where the leaked connection was created. [Null exception pa
ssed, creating stack trace for offending caller]
at weblogic.utils.StackTraceUtils.throwable2StackTrace(Ljava.lang.Throwa
ble;)Ljava.lang.String;(StackTraceUtils.java:28)
at weblogic.jdbc.wrapper.JTSConnection.finalizeInternal()V(JTSConnection
java:115)
at weblogic.jdbc.wrapper.JTSConnection_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(Unknow
n Source)
at java.lang.ref.Finalizer$FinalizerThread.run()V(Unknown Source)
at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Sourc
e)

thanks

karma

tester tester

unread,

Aug 24, 2004, 5:09:59 PM8/24/04

to

Thanks Joe.

I couldn't get the attachment here in newsgroups. Is it possible to email it to me to to_k...@yahoo.com.

Thanks

Karma

Joe Weinstein

unread,

Aug 24, 2004, 6:00:26 PM8/24/04

to tester tester

tester tester wrote:

Hi. I'll need a business email address. ka...@yahoo.com fails...
Joe

tester tester

unread,

Aug 24, 2004, 7:06:25 PM8/24/04

to

Thanks Joe.

I got the jar, but I couldn't see any useful stacktrace with this too. I am seeing the same error message originated from connection's finalize method.

I saw that the Statement class is included in the jar. Do I need Connection class too?

<Aug 24, 2004 10:53:58 PM GMT> <Warning> <JDBC> <BEA-001074> <A JDBC pool connec
tion 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 t
race at create shows where the leaked connection was created. [Null exception p
assed, creating stack trace for offending caller]

Nicholas Wee

unread,

Aug 27, 2004, 8:18:44 PM8/27/04

to

Hello Joe

Would appreciate if you can sent me the [81sp2conenv_pool.jar] debug jar too. I'm facing the same problem.

Thanks

Dany Auclair

unread,

Aug 31, 2004, 2:29:53 PM8/31/04

to

Hi Joe

We are using Ingres database and we have found the same kind of debug trace than some other with Oracle.

####<Aug 31, 2004 9:41:47 AM EDT> <Debug> <Common> <ssq87> <extsaacpro1> <Thread-6> <<WLS Kernel>> <> <BEA-000610> < RP(Ingres):timeoutInactiveRes (20)>
####<Aug 31, 2004 9:41:47 AM EDT> <Debug> <Common> <ssq87> <extsaacpro1> <Thread-6> <<WLS Kernel>> <> <BEA-000610> < RP(Ingres):timeoutInactiveRes (20)>
####<Aug 31, 2004 9:41:47 AM EDT> <Debug> <Common> <ssq87> <extsaacpro1> <Thread-6> <<WLS Kernel>> <> <BEA-000610> < RP(Ingres):timeoutInactiveRes (20)>
####<Aug 31, 2004 9:41:47 AM EDT> <Debug> <Common> <ssq87> <extsaacpro1> <Thread-6> <<WLS Kernel>> <> <BEA-000610> < RP(Ingres):timeoutInactiveRes (20)>
####<Aug 31, 2004 9:41:47 AM EDT> <Debug> <Common> <ssq87> <extsaacpro1> <Thread-6> <<WLS Kernel>> <> <BEA-000610> < RP(Ingres):timeoutInactiveRes (20)>
####<Aug 31, 2004 9:41:47 AM EDT> <Debug> <Common> <ssq87> <extsaacpro1> <Thread-6> <<WLS Kernel>> <> <BEA-000610> < RP(Ingres):timeoutInactiveRes (20)>
####<Aug 31, 2004 9:41:47 AM EDT> <Debug> <Common> <ssq87> <extsaacpro1> <Thread-6> <<WLS Kernel>> <> <BEA-000610> < RP(Ingres):timeoutInactiveRes (20)>
####<Aug 31, 2004 9:41:47 AM EDT> <Debug> <Common> <ssq87> <extsaacpro1> <Thread-6> <<WLS Kernel>> <> <BEA-000610> < RP(Ingres):timeoutInactiveRes (20)>
####<Aug 31, 2004 9:41:47 AM EDT> <Warning> <Common> <ssq87> <extsaacpro1> <Thread-6> <<WLS Kernel>> <> <BEA-000620> <Forcibly releasing inactive resource "weblogic.jdbc.common.internal.ConnectionEnv@175dce3" back into the pool "Ingres".>
####<Aug 31, 2004 9:41:47 AM EDT> <Warning> <Common> <ssq87> <extsaacpro1> <Thread-6> <<WLS Kernel>> <> <BEA-000620> <Forcibly releasing inactive resource "weblogic.jdbc.common.internal.ConnectionEnv@f8f12c" back into the pool "Ingres".>
####<Aug 31, 2004 9:41:47 AM EDT> <Warning> <Common> <ssq87> <extsaacpro1> <Thread-6> <<WLS Kernel>> <> <BEA-000620> <Forcibly releasing inactive resource "weblogic.jdbc.common.internal.ConnectionEnv@a2ad27" back into the pool "Ingres".>
####<Aug 31, 2004 9:41:47 AM EDT> <Debug> <Common> <ssq87> <extsaacpro1> <Thread-6> <<WLS Kernel>> <> <BEA-000610> < RP(Ingres):timeoutInactiveRes (20)>
####<Aug 31, 2004 9:41:47 AM EDT> <Debug> <Common> <ssq87> <extsaacpro1> <Thread-6> <<WLS Kernel>> <> <BEA-000610> < RP(Ingres):timeoutInactiveRes (30)>
####<Aug 31, 2004 9:41:47 AM EDT> <Warning> <JDBC> <ssq87> <extsaacpro1> <Thread-6> <<WLS Kernel>> <> <BEA-001153> <Forcibly releasing inactive connection "weblogic.jdbc.wrapper.PoolConnection_com_cariboulake_jsql_JSQLConnection@a65f" back into the connection pool "Ingres".>

Is it possible to send me 81sp2conenv_pool.jar

Do you have any instructions to configure that

Thank you

Dany

Joe Weinstein

unread,

Aug 31, 2004, 2:49:41 PM8/31/04

to

Dany Auclair wrote:

> Hi Joe

Show your pool config. This has nothing to do with that jar.
You have timout idle connections turned on. Turn it off. It
doesn't help.

Malini Kaushik

unread,

Sep 2, 2004, 6:30:19 PM9/2/04

to

Hi Joe,
Would appreciate it if you could send me the
81sp2conenv_pool.jar too. I have the exact same issue

thanks,
Malini

Joe Weinstein

unread,

Sep 2, 2004, 7:05:41 PM9/2/04

to

Malini Kaushik wrote:

Hi. Show me your symptoms. The jar has been attached to
previous posts. Send me a real email address.
Joe

michael mitchell

unread,

Sep 3, 2004, 5:41:11 PM9/3/04

to

Hello,

I'm also having this problem for wl8 sp3 could someone email me this jar.

thanks, michael

Joe Weinstein

unread,

Sep 3, 2004, 5:51:46 PM9/3/04

to michael mitchell

michael mitchell wrote:

Hi. there are a few places where this could occur, and both in 81sp2
and 81sp3, so please send me your server version and your exact
symptom (full stacktrace).
Joe

Guillermo Islas Chacón

unread,

Sep 14, 2004, 11:43:29 AM9/14/04

to

Joe,

Could you send me debug.jar file, please?

Thanks in advance.

Rajit Kavindran

unread,

Sep 17, 2004, 4:56:41 PM9/17/04

to

Joe,

I am having problems with getting into the site.
I also have the same problems, here is the stack -

<Aug 28, 2004 7:07:51 PM EDT> <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(StackTraceUtils.java:28)

at weblogic.jdbc.wrapper.PoolConnection.finalizeInternal(PoolConnection.java:84)

at weblogic.jdbc.wrapper.PoolConnection_COM_ibm_db2_jdbc_app_DB2Connection.finalize(Unknown Source)

at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)

at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83)

at java.lang.ref.Finalizer.access$100(Finalizer.java:14)

at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160)

>

And what is the impact of the following property on performance? "Remove Infected Connections Enabled". I have been trying to get more understanding on the web and does it option work on any connection? Or only on infected connection? And what would define an infected connection?

If you can send me the jar at the following id - rajit.k...@capitalone.com that would be great.

Thanks,

Rajit.

Rajit Kavindran

unread,

Sep 17, 2004, 7:05:01 PM9/17/04

to

Joe,

Thanks for your reply.
The version I am running is - Version: WebLogic Server 8.1 SP3 Do you have any recommendations around - Single Threaded Servlet Pool Size:?

Thanks,

Rajit.

David Cuesta

unread,

Sep 22, 2004, 3:17:40 AM9/22/04

to

Hi Joe,

I have the same problem as Anthony, could you send me the 81sp2conenv_pool.jar or explain me how download it from forum?,

thanks a lot,

dcuesta...@yahoo.es

Swee Yueng Fun

unread,

Sep 27, 2004, 5:42:20 AM9/27/04

to

Hi Joe,

I am using Bea Weblogic 8.1 sp3 and facing the same connection leak problem, here is the stack:

<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.JTSConnection.finalizeInternal()V(JTSConnection.java:115)

at weblogic.jdbc.wrapper.JTSConnection_weblogic_jdbc_mssqlserver4_MicrosoftConnection.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)

I know you have the jar which can show the actual trace of the creation of the connection right? Can you please send to me? Thanks a lot.

Mik Tuver

unread,

Sep 27, 2004, 6:55:02 AM9/27/04

to

Hi...

The jar you posted worked nicely for me...
Found that (ofcaurse) have to close connection after handling some
resultsets :-)

Thanx

Mik Tuver

Binu Kuruvilla

unread,

Sep 27, 2004, 12:00:48 PM9/27/04

to

Hi Joe,

Could you please send the debug jar to trace the connection leaks

Thanks in advance

my email address : kur...@yahoo.com

Swee Yueng Fun

unread,

Sep 27, 2004, 11:51:37 PM9/27/04

to

sweeyu...@hotelinfosys.com

Thx a lot.

Chhimi Bist

unread,

Sep 28, 2004, 6:09:14 AM9/28/04

to

Hi Joe,

Could you please send the debug jar to trace the connection leaks

Thanks in advance

my email address : chhim...@tcs.com

Chhimi Bist

unread,

Sep 28, 2004, 6:45:40 AM9/28/04

to

Hi Joe,
Even i am facing the problem of connection leaks.
Please send me the debug.jar at this ID chhim...@tcs.com
I am working with WLS 8.1 SP3

Thanks in advance,
Chhimi

Swee Yueng Fun

unread,

Sep 28, 2004, 8:37:36 PM9/28/04

to

Hi Joe,

Can you please send the jar file to me again? I can't receive it coz it is high risk extension file. Can you please zip it and send again? Can I download the file from bea website? Sorry for the trouble.

Anyone else who got the jar file, can you guys zip it and send to me? I need it urgently. Thanks a lot :)

P/S: I'm using weblogic 8.1 sp3. Email: sweeyu...@hotelinfosys.com

Jagdish Patil

unread,

Sep 30, 2004, 3:51:03 PM9/30/04

to

hi Joe,

Could you please send me the jar file. my mail id is

Jagdis...@med.ge.com

We are using weblogic8.1/sp2.

Here is the stack trace.
[SerialConnection] : Connection Leak detected! java.lang.Throwable: [Null exception passed, creating stack trace for offending caller]
at weblogic.utils.StackTraceUtils.throwable2StackTrace(StackTraceUtils.java:28)
at weblogic.jdbc.rmi.SerialConnection.finalize(SerialConnection.java:84)

at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83)
at java.lang.ref.Finalizer.access$100(Finalizer.java:14)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160)

[SerialConnection] : Connection Leak detected! java.lang.Throwable: [Null exception passed, creating stack trace for offending caller]
at weblogic.utils.StackTraceUtils.throwable2StackTrace(StackTraceUtils.java:28)
at weblogic.jdbc.rmi.SerialConnection.finalize(SerialConnection.java:84)

Joe Weinstein

unread,

Sep 30, 2004, 4:16:55 PM9/30/04

to

Jagdish Patil wrote:

> hi Joe,
>
> Could you please send me the jar file. my mail id is
>
> Jagdis...@med.ge.com
>
> We are using weblogic8.1/sp2.

Sure, but this is a slightly different case, it seems.
The exception you're getting below seems to be from
an external client, not from the Weblogic jvm, is that
correct?
thanks
Joe

Jagdish Patil

unread,

Sep 30, 2004, 6:55:56 PM9/30/04

to

Thanks for reply.

I believe this is from Weblogic JVM.

We have eds-database.jar which is wrapper around jdbc api and it makes use of weblogic connection pool,
this connection pool resides on diffrent weblogic server. We use wrapper api's from this jar file in our web application which resides on another server to perform database logging functionality

This stack trace is from our weblogic console when ever our servelt calls database api's are from eds.database.jar file.

Hope this helps to visualize our issue.

Any inputs are highly appreciated.

Regards,
Jagdish

Joe Weinstein

unread,

Sep 30, 2004, 10:55:09 PM9/30/04

to

Jagdish Patil wrote:

Yes. it seems one server is getting pool connections (RMI proxies) from another server.
So did your warning show up on the server with the original pool, or in the 'client' weblogic?
thanks,
Joe
(and what version of weblogic again?)

Jagdish Patil

unread,

Oct 1, 2004, 12:29:42 PM10/1/04

to

Yes ... this is what we are getting at Client weblgoic when we first time access database api's which connect to
our connection pool weblogic server and after this we start getting connection leak issues.

sql = SELECT FACILITYID, FACILITYNAME FROM UCM.UCM_FACILITY WHERE HPG_FLAG='Y' ORDER BY FACILITYNAME
java.rmi.NoSuchObjectException: Unable to dispatch request to Remote object with id: '280'. The object has been garbage collected.

Start server side stack trace:
java.rmi.NoSuchObjectException: Unable to dispatch request to Remote object with id: '280'. The object has been garbage collected.
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:766)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:738)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:207)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:777)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:508)
at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:770)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:694)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
End server side stack trace

at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
at weblogic.jdbc.rmi.internal.ConnectionImpl_WLStub.rollback(Unknown Source)
at weblogic.jdbc.rmi.SerialConnection_weblogic_jdbc_rmi_internal_ConnectionImpl_WLStub.rollback(Unknown Source)
at com.ge.med.service.dataservices.DAC.SQL.SelectClass.executeQuery(SelectClass.java:244)
at com.ge.med.service.dataservices.DAC.SQL.QueryHandler.executeQuery(QueryHandler.java:273)
at com.ge.med.service.icenter.em.util.SearchCustomer.getCustomerList(SearchCustomer.java:77)
at jsp_servlet.__hpg_bottom._jspService(__hpg_bottom.java:217)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:446)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
--------------- nested within: ------------------
weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested exception:
[java.rmi.NoSuchObjectException: Unable to dispatch request to Remote object with id: '280'. The object has been garbage collected.

Start server side stack trace:
java.rmi.NoSuchObjectException: Unable to dispatch request to Remote object with id: '280'. The object has been garbage collected.
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:766)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:738)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:207)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:777)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:508)
at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:770)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:694)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
End server side stack trace
]
at weblogic.jdbc.rmi.internal.ConnectionImpl_WLStub.rollback(Unknown Source)
at weblogic.jdbc.rmi.SerialConnection_weblogic_jdbc_rmi_internal_ConnectionImpl_WLStub.rollback(Unknown Source)
at com.ge.med.service.dataservices.DAC.SQL.SelectClass.executeQuery(SelectClass.java:244)
at com.ge.med.service.dataservices.DAC.SQL.QueryHandler.executeQuery(QueryHandler.java:273)
at com.ge.med.service.icenter.em.util.SearchCustomer.getCustomerList(SearchCustomer.java:77)
at jsp_servlet.__hpg_bottom._jspService(__hpg_bottom.java:217)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:446)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

[SerialConnection] : Connection Leak detected! java.lang.Throwable: [Null exception passed, creating stack trace for offending caller]
at weblogic.utils.StackTraceUtils.throwable2StackTrace(StackTraceUtils.java:28)
at weblogic.jdbc.rmi.SerialConnection.finalize(SerialConnection.java:84)
at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83)
at java.lang.ref.Finalizer.access$100(Finalizer.java:14)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160)

2004-10-01 11:16:19,393 [ExecuteThread: '12' for queue: 'weblogic.kernel.Default'] {SelectClass:executeQuery:220} WARN - executeQuery():sql time:3369
In SearchCustomer.getCustomerList , Exception is: Unexpected Exception
<Oct 1, 2004 11:16:19 AM CDT> <Error> <HTTP> <BEA-101017> <[ServletContext(id=24349308,name=icenter,context-path=/icenter)] Root cause of ServletException.
java.lang.Exception
at com.ge.med.service.icenter.em.util.SearchCustomer.getCustomerList(SearchCustomer.java:85)
at jsp_servlet.__hpg_bottom._jspService(__hpg_bottom.java:217)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:446)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

Jason Goris

unread,

Oct 1, 2004, 1:25:37 PM10/1/04

to

Joe,

I have been seeing the same error messages with very similar stack dumps. I am using WLS 8.1.2 and oracle 9.2.x driver. I think I need the 81sp2conenv_pool.jar file emailed to me. Please send me the file. thanks!

jason...@crowncastle.com

Thanks,

Jason

Jason Goris

unread,

Oct 1, 2004, 4:48:30 PM10/1/04

to

Thanks.

I turned on some WLS debugging and see the following when the connection leak occurs:

####<Oct 1, 2004 4:38:04 PM EDT> <Warning> <JDBC> <CCIC5748> <localDev> <Finalizer> <<anonymous>> <> <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. JTAConnection leaked due to using it in non-xa mode without close it.> ####<Oct 1, 2004 4:38:04 PM EDT> <Debug> <JDBC XA> <CCIC5748> <localDev> <Finalizer> <<anonymous>> <> <000000> < -tx:null- -pool:iSitePool- > JTA Connection.close - conn:[weblogic.jdbc.wrapper.JTAConnection_weblogic_jdbc_wrapper_XAConnection
_oracle_jdbc_driver_LogicalConnection-iSitePool-260, null]> ####<Oct 1, 2004 4:38:04 PM EDT> <Debug> <JDBC XA> <CCIC5748> <localDev> <Finalizer> <<anonymous>> <> <000000> < -tx:null- -pool:iSitePool- < JTA Connection.close>

However, I never see any stack trace in any of my log files?!?! Where is this supposed to be displayed/logged to?

Any ideas?

Some settings in my startWeblogic.cmd command:

set
CLASSPATH=D:\bea\user_projects\domains\localDomain\81sp2whereclosed.jar;D:\b
ea\user_projects\domains\localDomain\ojdbc14.jar;D:\bea\user_projects\domain
s\localDomain\jt400.jar;%WEBLOGIC_CLASSPATH%;%POINTBASE_CLASSPATH%;%JAVA_HOM
E%\jre\lib\rt.jar;%WL_HOME%\server\lib\webservices.jar;D:\bea\user_projects\
domains\localDomain;%CLASSPATH%

set JAVA_OPTIONS=-Xdebug -Xnoagent
-Xrunjdwp:transport=dt_socket,server=y,address=7777,suspend=n -Djava.compiler=NONE

%JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -Dweblogic.Name=%SERVER_NAME% -Djava.compiler=NONE -Dweblogic.ProductionModeEnabled=%PRODUCTION_MODE%
-Djava.security.policy="%WL_HOME%\server\lib\weblogic.policy"
-Dccic.environ=dev -Dlog4j.configuration=config/dev/log4j.properties
-DdomainLogDir=D:\bea\user_projects\domains\localDomain\logs
-Dweblogic.Debug=weblogic.JDBCConn="true",weblogic.JTAJDBC="true"
-DinstanceLogDir=D:\bea\user_projects\domains\localDomain\localDev\logs
weblogic.Server

..

And here is what I see on the console at server startup (as expected):

D:\bea\user_projects\domains\localDomain>startweblogic

CLASSPATH=D:\bea\user_projects\domains\localDomain\81sp2whereclosed.jar;D:\b
ea\u
ser_projects\domains\localDomain\ojdbc14.jar;D:\bea\user_projects\domains\lo
calD
omain\jt400.jar;C:\J2SDK1~1.2_0\lib\tools.jar;C:\bea\WEBLOG~1\server\lib\web
logi
c_sp.jar;C:\bea\WEBLOG~1\server\lib\weblogic.jar;C:\bea\WEBLOG~1\server\lib\
ojdb
c14.jar;C:\bea\WEBLOG~1\common\eval\pointbase\lib\pbserver44.jar;C:\bea\WEBL
OG~1
\common\eval\pointbase\lib\pbclient44.jar;C:\J2SDK1~1.2_0\jre\lib\rt.jar;C:\
bea\
WEBLOG~1\server\lib\webservices.jar;D:\bea\user_projects\domains\localDomain
;C:\
j2sdk1.4.2_04\lib\tools.jar;D:\Projects\CCIsites\src\external\junit\3.8.1\ju
nit.
jar;D:\Projects\CCIsites\src\external\bea\wlserver8.1\lib\weblogic.jar;D:\Pr
ojec
ts\CCIsites\src\external\bea\wlserver8.1\lib\webservices.jar

PATH=C:\bea\WEBLOG~1\server\bin;C:\J2SDK1~1.2_0\jre\bin;C:\J2SDK1~1.2_0\bin;
C:\j
2sdk1.4.2_04\bin;D:\Projects\CCIsites\src\external\ant\1.5.1\bin;C:\WINDOWS\
SYST
EM32;;C:\bea\WEBLOG~1\server\bin\oci920_8

Thanks,

Jason Goris
Crown Castle International
Pittsburgh, PA

Slava Imeshev

unread,

Oct 2, 2004, 5:45:05 PM10/2/04

to

Jagdish,

"Jagdish Patil" <noad...@noaddress.given> wrote in message news:30431552.1096648212929.JavaMail.root@jserv5...

> Yes ... this is what we are getting at Client weblgoic when we first time access database api's which connect to
> our connection pool weblogic server and after this we start getting connection leak issues.
>
> sql = SELECT FACILITYID, FACILITYNAME FROM UCM.UCM_FACILITY WHERE HPG_FLAG='Y' ORDER BY FACILITYNAME
> java.rmi.NoSuchObjectException: Unable to dispatch request to Remote object with id: '280'. The object has been garbage collected.

A cause of this may be that your client didn't access weblogic
for a long time and the server considered the client dead and
released resources accociated with the request.

Is it possible that you have opened a connection on a remote
client, left it unused for a long time and then tried to use it again?

Please check this for handling JDBC in weblogic:
http://www.viewtier.com/newsgroups/thread.jspa?threadID=1&tstart=0

Regards,

Slava Imeshev

Jagdish Patil

unread,

Oct 5, 2004, 4:01:28 PM10/5/04

to

Thanks for the replies. It looks like we have diffrent service packs installed on client and server weblogic instances.
When we upgraded our server to SP2 this leak issue disappeared. I am not sure whether SP2 has fix in it or weblogic81. behaves strange with diffrent service packs.

DANAPPA KORI

unread,

Oct 6, 2004, 7:09:53 AM10/6/04

to

Please send me 81sp2conenv_pool.jar file, if you have.
if you send it at earliest it could help us a lot

pls use the below mail id to send the same

dik...@rediffmail.com

With reg,
Kori

DANAPPA KORI

unread,

Oct 6, 2004, 7:12:46 AM10/6/04

to

joe,

Could you send me 81sp2conenv_pool.jar for the same? we are using WL81 sp2.
pls use below id to send the same

dik...@rediffmail.com

With reg,
Kori

Paul DiMarco

unread,

Oct 11, 2004, 3:08:34 PM10/11/04

to

Hi Joe,
I'm using weblogic 8.1 sp3, and have the same problem
<Oct 11, 2004 1:54:00 PM EDT> <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(StackTraceUtils.java:28)
at weblogic.jdbc.wrapper.JTSConnection.finalizeInternal(JTSConnection.java:115)
at weblogic.jdbc.wrapper.JTSConnection_oracle_jdbc_driver_OracleConnection.finalize(Unknown Source)

at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83)
at java.lang.ref.Finalizer.access$100(Finalizer.java:14)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160)

Could you send me your debug jar "81sp2connenv_pool.jar".
Thanks.

Joe Weinstein

unread,

Oct 11, 2004, 4:03:26 PM10/11/04

to Paul DiMarco

It's been posted to the group several times. If you can't find it, send me a real email address.
Joe

Paul DiMarco

unread,

Oct 11, 2004, 4:41:52 PM10/11/04

to

Thanks Joe. I can't find this debug.jar from this email group. I opened BEA support case 536934 for this. Could you send me the *.jar through this support case.
Thanks

Narendar doshi

unread,

Oct 14, 2004, 7:56:28 AM10/14/04

to

Hi joe,
Can you please send me 81sp2conenv_pool.jar file, if you have.if you
send it at earliest it could help us a lot you can send the jar at
narenda...@armaninfotech.com, we are using WL8.1 with sp3 in linux
and as well as in Windows. i am getting the following error message

####<Oct 14, 2004 4:50:15 PM IST> <Warning> <JDBC> <linuxoracle>
<myserver> <Finalizer> <<anonymous>> <> <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_weblogic_jdbc_oracle_OracleConnection.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)

Thanks
Narendar

Narendar doshi

unread,

Oct 15, 2004, 6:28:39 AM10/15/04

to

Zhihong Yu

unread,

Oct 31, 2004, 5:40:38 PM10/31/04

to

Hi,
I cannot access case 536934.
I have created case 541364 .
Please send me debug.jar

Joe Weinstein

unread,

Nov 1, 2004, 12:25:09 AM11/1/04

to Zhihong Yu

Give us (me) a valid email address.
Joe

murali kaza

unread,

Nov 1, 2004, 10:32:22 AM11/1/04

to

Joe,

Can you please send the wl81sp2_conenv.jar to the following address I am getting the same problem.

Murali

murali kaza

unread,

Nov 1, 2004, 10:33:16 AM11/1/04

to

Joe,

Can you please send the wl81sp2_conenv.jar to the following address I am getting the same problem.

kaz...@dteenergy.com

Murali

Lynn Taylor

unread,

Nov 2, 2004, 1:25:47 PM11/2/04

to

I'm afraid I'm unable to get the jar from the news group. Would I be able to get a copy for 8.1 SP3, please?

Thank you!

Lynn Taylor

unread,

Nov 2, 2004, 1:34:11 PM11/2/04

to

Please disregard this request. I managed to get the jar through a
different news reader.

Thanks,
Lynn

Stephen Ross

unread,

Nov 9, 2004, 10:51:29 AM11/9/04

to

Hi Joe,

I'm another person trying to track down a connection leak and unable to download the 81sp2conenv_pool.jar file.

If you could mail it to me that would be much appreciated.

Thanks

stephe...@lehman.com

Using: Weblogic 8.1 SP3 with Sybase

Rayy Choi

unread,

Nov 9, 2004, 9:05:38 PM11/9/04

to

Dear Joe,
I had got your jar(81sp3whereleaked.jar),
and now I getting the below Exception,
I also can't find where the connction leaked,
Can you help me?

<2004-11-10 上午09时59分43秒 CST> <Warning> <JDBC> <BEA-001074> <A JDBC pool con

nection leak was detected. A connection leak occurs when a connection obtained f
rom 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 stac

k trace at create shows where the leaked connection was created. Stack trace at
connection create:

at weblogic.jdbc.wrapper.PoolConnection.init(PoolConnection.java:56)
at weblogic.jdbc.pool.Driver.allocateConnection(Driver.java:254)
at weblogic.jdbc.pool.Driver.connect(Driver.java:164)
at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:507)
at weblogic.jdbc.jts.Driver.connect(Driver.java:139)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSour
ce.java:305)
at weblogic.jdbc.common.internal.RmiDataSource_WLSkel.invoke(Unknown Sou
rce)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerR
ef.java:108)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
144)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:415)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
java:30)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
>

Rayy Choi

unread,

Nov 9, 2004, 9:37:21 PM11/9/04

to

Thanks for reply.

I am using one Weblogic, and a Tomcat Client.

Rayy

> Hi. Are you in a cluster, of are you connecting from
> one weblogic server to another?
> Joe
> >
>

Joe Weinstein

unread,

Nov 10, 2004, 12:39:03 PM11/10/04

to

Rayy Choi wrote:

> Thanks for reply.
>
> I am using one Weblogic, and a Tomcat Client.
>
> Rayy
>

Ok, then let's see your code that gets connections in
tomcat. I suspect you aren't closing connections.
Joe

Rayy Choi

unread,

Nov 10, 2004, 8:15:28 PM11/10/04

to

> Ok, then let's see your code that gets connections in
> tomcat. I suspect you aren't closing connections.
> Joe

Thanks for reply.

I had found out the unclose connections in tomcat.

I didn't know there had some connections in the Tomcat,
so I have not check the client code before.

Thanks,

Rayy

Joe Weinstein

unread,

Nov 10, 2004, 11:26:50 PM11/10/04

to

Rayy Choi wrote:

Glad to help.
Joe

Arun Sreekantan

unread,

Nov 15, 2004, 4:29:52 AM11/15/04

to

Hi Joe

Can you send the debug patch for identifying the class which has not closed the connection properly.
I have already enbaled Connection Leak Profiling

I am getting the following error in the application

<Warning> <JDBC> <BEA-001074> <A JDBC pool c

onnection leak was detected. A connection leak occurs when a connection obtained from the pool was not closed explicitly by calling close() and then was dispose
d by the garbage collector and returned to the connection pool. The following stack trace at create shows where the leaked connection was created. [Null except

ion passed, creating stack trace for offending caller]

Thanks
Arun
arun.sr...@gmail.com

Jam wenny

unread,

Nov 15, 2004, 9:46:53 AM11/15/04

to

hi, joe,
I have the same problem as 'connection leak', and I have enabled the connection leak profiling, but it seems does little help to me.
So, could u do me a favor and send the debug patch to me?
And I use weblogic813.

I have no business email address, could u try this one?
zhe...@gmail.com

best regards!

Alejandro Rico

unread,

Nov 18, 2004, 9:31:56 PM11/18/04

to

Hello Joe,

Sorry for the inconvinience; I had previously posted a reply for another message, but after reading the whole thread I'm wishing you could help me.

I would appretiate if you send me the debug jar to a_r...@yahoo.com

Thanks for your Help

Alex

Alejandro Rico

unread,

Nov 18, 2004, 9:13:34 PM11/18/04

to

Hello Timmas;

Did you got the jars?
Can you send them to a_r...@yahoo.com ?

Because I am having trouble with Connection Leaking too.

Thanks

Alex

Alejandro Rico

unread,

Nov 19, 2004, 11:28:06 AM11/19/04

to

I am Using Weblogic 8.1 SP3

Thanks

Max Monterrey

unread,

Nov 29, 2004, 6:58:25 PM11/29/04

to

WHere can I get a copy of 81sp3whereleaked.jar? Please email it to me at max.mo...@oomc.com

Thank you

Max Monterrey

unread,

Nov 30, 2004, 2:36:29 PM11/30/04

to

Joe, I applied the patch you provided and put the jar after the weblogic.jar and it is not working for me. I am not able to trace what is creating the memory leak. Any help would be appreciated.

BEA-001074 Nov 30, 2004 11:16:01 AM PST REALM_MS1 Warning JDBC 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.JTAConnection.finalizeInternal()V(JTAConnection.java:328)
at weblogic.jdbc.wrapper.JTAConnection_weblogic_jdbc_wrapper_XAConnection_weblogic_jdbcx_base_BaseConnectionWrapper.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)

BEA-001074 Nov 30, 2004 11:16:01 AM PST REALM_MS1 Warning JDBC 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. JTAConnection leaked due to using it in xa mode without close it.

Joe Weinstein

unread,

Nov 30, 2004, 3:49:03 PM11/30/04

to

Show me the classpath that the weblogic startup script prints out when it starts the server.
This is 81sp2 or sp3?
thanks
joe

Preeti Gupta

unread,

Dec 1, 2004, 12:41:54 AM12/1/04

to

Hi Joe,

Could u pls send me the required jar file as i'm also facing the same problem.

My email address is:
preeti...@siemens.com

Thanks

Joe Weinstein

unread,

Dec 2, 2004, 6:27:24 PM12/2/04

to

Vaishali Mahale wrote:

> Hi,
>
> I'm using weblogic 8.1 with sp3 and getting the same exception. Can you send me the debug jar for 8.1/sp3.
>
> Thanks

When we get a valid email address... Say what weblogic version. Show the symptoms....
Joe

Vaishali Mahale

unread,

Dec 2, 2004, 6:25:48 PM12/2/04

to

Shao Chen

unread,

Dec 3, 2004, 12:40:12 PM12/3/04

to

Hi Joe,

We have the same issue with our application as well.
Can you send me the 81sp2conenv_pool.jar?
My email address is jsc...@yahoo.com

James Liu

unread,

Dec 5, 2004, 9:24:59 AM12/5/04

to

Hi Joe,
Can you please send the 81sp2conenv_pool.jar and also the debug jar which others are using to the following address spri...@yahoo.com.

I got the same error in Weblogic 81sp2 which seem to be killing the server.

Thanks a lot,
James

Joe Weinstein

unread,

Dec 5, 2004, 4:44:51 PM12/5/04

to

mail to spri...@yahoo.com bounced.

Raju Vage

unread,

Dec 6, 2004, 9:42:08 AM12/6/04

to

Hi Joe,

I am getting the following stack trace with Weblogic 8.1sp3.

<Dec 6, 2004 8:35:11 AM 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(StackTraceUtils.j
ava:28)
at weblogic.jdbc.wrapper.JTSConnection.finalizeInternal(JTSConnection.ja
va:115)
at weblogic.jdbc.wrapper.JTSConnection_oracle_jdbc_driver_T4CConnection.
finalize(Unknown Source)
at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83)
at java.lang.ref.Finalizer.access$100(Finalizer.java:14)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160)
>

Is your debug patch help me in to catch connection leak in the code? Can you send me the debug patch to the following email addressses.

rv...@yahoo.com
raju...@thehartford.com

Thanks
Raju

Vaishali Mahale

unread,

Dec 6, 2004, 9:02:37 PM12/6/04

to

After migrating to weblogic 8.1 with sp3, I am getting the following warning message -

<Dec 6, 2004 4:44:46 PM PST> <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(StackTraceUtils.java:28)
at weblogic.jdbc.wrapper.JTSConnection.finalizeInternal(JTSConnection.java:115)

at weblogic.jdbc.wrapper.JTSConnection_oracle_jdbc_driver_T4CConnection.finalize(Unknown Source)

at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83)
at java.lang.ref.Finalizer.access$100(Finalizer.java:14)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160)
>

I have enabled connection leak profiling, but still the stack trace does not give me more information on the conenction leak.

Also I only see this warning when I use the JDBCTxDataSource.

Can you send me a patch (for weblogic 8.1/sp3 ) which will help me to detect all the connection leaks.

Here's my email id - vaishal...@neoforma.com

Thanks,
Vaishali.

fdas fdas

unread,

Dec 13, 2004, 7:49:44 AM12/13/04

to

Hi Joe,
Would appreciate it if you could send me the
81sp2conenv_pool.jar
81sp3wrapsta_whereclosed.jar
debug.jar
too. I have the exact same issue

my email is coolkn...@sina.com

thanks,
Malini

Davis Peden

unread,

Dec 13, 2004, 8:58:19 PM12/13/04

to

Joe- Sounds like you are the connection pool leak man!

I am having a connection pool leak on WLP 8.1 sp3 and I was hoping you could email me your debug jar to help me pinpoint my issue. Please use: samuel....@accenture.com

Thank you!

Paul Weyers

unread,

Dec 14, 2004, 8:45:24 PM12/14/04

to

Got the same problem on 81SP3. Joe please send me the debug .jar. My email address is paul.we...@cyf.govt.nz. Thanks in advance for this

William Louth

unread,

Dec 19, 2004, 2:17:53 PM12/19/04

to

Hi,

Just wanted to inform you that our product JDBInsight ( JXInsight) has had connection, statement, and resultset leakage in the product for more than 2 years and works with all versions of BEA WebLogic Server as well as other containers and custom framework code. We provide stack traces, code sources, sql, and transaction context for every leakage.

The product can be downloaded from: http://www.jinspired.com/products/jdbinsight/downloads/index.html

Chapter 5 – Resource Perspective and Views: http://www.jinspired.com/products/jdbinsight/userguide.pdf

We have recently provided an update to our 3.0 release that includes an additional document describing the integration steps in getting JDBInsight/JXInsight profiling and monitoring BEA WebLogics Sample Medical Records (XA) J2EE Application: http://www.jinspired.com/products/jdbinsight/medrecguide.pdf

Regards,

William Louth
Product Architect
JInspired

"J2EE tuning, testing and tracing with real Insight"
http://www.jinspired.com

Shishank Mathur

unread,

Dec 29, 2004, 2:08:00 AM12/29/04

to

Hi Joe,

Got the same problem with Weblogic 8.1 SP3. Can you please send me the patch. My email address is shis...@yahoo.com.
Thanks in advance,

Kind Regards,
Shishank

Joe Weinstein

unread,

Dec 29, 2004, 12:51:53 PM12/29/04

to

Shishank Mathur wrote:

Hi. For any customer getting logged warnings like:

####<Jul 20, 2004 11:53:10 AM EDT> <Warning> <JDBC> <bigshop>
<myCluster> <Finalizer> <<anonymous>> <> <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]

For WebLogic Server versions 8.1sp2 and 8.1sp3 there is a bug in the JTS/JTA
connections that creates an unhelpful exception when a connection is leaked.
There is supposed to be a stacktrace that shows where the connection was made,
in order to help trace the leak. For sp2 and sp3, there is instead a 'null'
stacktrace because these classes neglected to retain a 'where-created' trace
when they were initialized.

The official patches should be obtained by contacting support, and asking
for CR189281_81sp3.3.jar for 81sp3, or CR209251_81sp2.jar for 81sp2.

Please install this patch so it comes ahead of the weblogic.jar in the
classpath constructed by the startWebLogic script.
With this jar, these warnings will only be logged if leak tracing is
turned on for the pool, and they will contain the useful trace they intended
to have.

Joe

hardeep arora

unread,

Dec 30, 2004, 11:42:18 AM12/30/04

to

Could someone please send me the patch for debugger
for detecting connection leaks.
I m getting the following stack trace:
[SerialConnection] : Connection Leak detected! java.lang.Throwable: [Null except

ion passed, creating stack trace for offending caller]

at weblogic.utils.StackTraceUtils.throwable2StackTrace(StackTraceUtils.j
ava:28)
at weblogic.jdbc.rmi.SerialConnection.finalize(SerialConnection.java:84)

at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83)
at java.lang.ref.Finalizer.access$100(Finalizer.java:14)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160)

Thanks,
Hardeep
har...@tiaa-cref.org

hardeep arora

unread,

Dec 30, 2004, 11:35:58 AM12/30/04

to

Could someone please email me the patch for debugging connection leaks ie 81sp3whereleaked.jar..
Will appreciate your help.
Thanks,
Hardeep arora
har...@tiaa-cref.org

hardeep arora

unread,

Dec 30, 2004, 11:35:22 AM12/30/04

to

subrata mu

unread,

Jan 18, 2005, 3:32:26 PM1/18/05

to

Hi,
Please chec in your code, all the open connections you are closing properly or not. Connection leak occurs when all the open connectiosn are not closed using close() API call

piyushk...@gmail.com

unread,

Mar 17, 2019, 11:48:36 AM3/17/19

to

Hello Sir,

Kindly help me to resolve this issue..my email id is piyushk...@gmail.com

<Warning> <JDBC> <BEA-001594> <Forcibly releasing an already closed connection "weblogic.jdbc.wrapper.PoolConnection_oracle_jdbc_driver_T4CConnection@3c4" back into the data source connection pool "xcenterreplication".>

Thanks
Piyush