I found the message. Calling the GC before every executeQuery() seemed to reduce the problem, but it's still there. I'm going to switch to another DB, maybe MySQL or some other. I wellcome suggestions. The problem is I can't buy a RDBMS(or a JDBC driver) because the webapplication I'm developping is a college assignment. If any of you knows of a RDBMS that is easy to use, supports JDBC (without critical flaws like Access) and it's free, let me know. Thanks. ----- Mensaje original ----- De: Lacerda, Wellington (AFIS) <[EMAIL PROTECTED]> > Take a look on the list's history, because I saw something like you're > describing related with (possible) memory leaks in JDBC-ODBC (not sure > that's the problem), memory consumption and consequent performance > degradation and even TOMCAT crashing.
- TOMAT slowing down a lot after a while Federico Tello Gentile
- RE: TOMAT slowing down a lot after a while Lacerda, Wellington (AFIS)
- java.awt package Leon Palermo
- Re: java.awt package Nick Holloway
- Re: java.awt package Leon Palermo
- Re: java.awt package Nick Holloway
- RE: java.awt package Ed Gomolka
- RE: TOMAT slowing down a lot after a w... Federico Tello Gentile
- RE: TOMAT slowing down a lot after... John Bateman
- Re: TOMAT slowing down a lot a... Julio Serje (@Canada)
- RE: TOMAT slowing down a ... Federico Tello Gentile
- Re: TOMAT slowing dow... Kurt Bernhard Pruenner
- Re: TOMAT slowing down a lot after... Paul Russell
- Re: TOMAT slowing down a lot a... Ted Husted
- Re: TOMAT slowing down a ... Paul Russell
- RE: TOMAT slowing down a lot after a while August Detlefsen
- RE: TOMAT slowing down a lot after a w... Federico Tello Gentile
