commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 33591] - [dbcp][PATCH] Connection leak in PoolableConnection.close() (Oracle 10g driver)
Date Wed, 08 Mar 2006 05:24:28 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33591>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33591





------- Additional Comments From sjr@jdns.org  2006-03-08 05:24 -------
Created an attachment (id=17846)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=17846&action=view)
Possible testcase to illustrate bug

Hi there,

The testPoolableConnectionLeak method in this test case *may* illustrate the
bug. It shows that the connection pool has a getNumActive() equal to 1 even
after calling PoolableConnection.close() with already closed delegate
connection.

Applying Huw's patch shows no active objects in the connection pool after the
connection is closed. This is what I'd *expect* to happen, but correct me if
I'm wrong...

I am new to DBCP and I might not completely understand the issue, so if
somebody with more experience with these classes could check this out, that'd
be cool.

Thanks!

Regards,
James

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message