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.



Reply via email to