But depending on the DB, it can cause problems from the DB with too many open ResultSets... I had an issue with performance testing where everything but ResultSets were being closed and the Oracle DB started throwing errors after about 500 queries. Better safe than sorry.
-----Original Message----- From: Greg Ward [mailto:[EMAIL PROTECTED] Sent: Thursday, September 04, 2003 9:05 AM To: Tomcat Users List; [EMAIL PROTECTED] Subject: Re: Memory leaks? On 03 September 2003, Jim Lynch said: > OK, that's probably what's going on. I know I should close Statements > and Connections and do normally but I'm fairly certain I've some out > there dangling. I didn't know you had to close ResultSets, however. > Glad to know that. You don't have to close ResultSets -- check the JDBC docs: http://java.sun.com/j2se/1.4.2/docs/api/java/sql/Statement.html#close() (Closing a Statement also closes any open ResultSets associated with that Statement.) Greg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
