Per the javax.sql javadocs... When a Connection is closed it closes any open Statements. When a Statement is closed, it closes any open ResultSets.
If you just dereference a connection (non connection pool) when the Connection is GC'd it is closed. If you use DBCP 1.0 as your connection pool it tracks Statements and ResultSets used by a connection. When you close the connection it will ensure the Statements and ResultSets still open for that Connection are closed. Regards, Glenn Michael Nicholson wrote: > Well, I guess the subject line says it all. I'm having memory issues, and having >read the OOM error messages on the list, I've checked and found some open and not >being closed connections, so I'm going back and closing them all. The question is do >I need to explicitly close/dereference (set to null) all statements and recordsets >too? Right now the system takes about 4% of my available memory just for the beans >in question, so I'm trying to minimize what I store so that I could conceptually have >more than one user. > > Thanks in advance, > Mike Nicholson -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
