[ http://issues.apache.org/jira/browse/DBCP-180?page=all ]
Phil Steitz updated DBCP-180: ----------------------------- Bugzilla Id: (was: 31569) Fix Version/s: 1.3 If a safe and efficient patch is submitted to enable this enhancement, we can include it in 1.3. Per Yoav's comment, the patch should not rely on AbandonedTrace. > [dbcp] Dbcp doesn't meet JDBC specification > ------------------------------------------- > > Key: DBCP-180 > URL: http://issues.apache.org/jira/browse/DBCP-180 > Project: Commons Dbcp > Issue Type: Improvement > Affects Versions: 1.2 > Environment: Operating System: other > Platform: All > Reporter: Rohan Lenard > Priority: Minor > Fix For: 1.3 > > > The JDBC specification says for ResultSet and Statement that the ResultSet > and > Statement will be automatically closed when garbage collected. > This means that people often write code like this > Connection.getStatement().executeSQL("...."); > However, because the DelegateConnection/DelegateStatement/DelegateResultSet > extend AbandonedTrace (and are linked into the abandoned trace mechanism) > they > will not be garbage collected until the connection is closed. > This of course means that DBCP holds on to lots of memory that it shouldn't > do > (I've had people complain to me of memory leaks). > Surely it's possible to make the DelegateXX hold onto something else which > does > the AbandonedTrace and so when it is released it can do the implicit close > and > then everything will be coool. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]