Hi,
I'm running a small app. with Tomcat and JDBC connections to MS Access, and
have had no problems at all, so I think you may be doing something wrong (or
ommiting something). As a general recommendation (I'm sorry if it sounds
stupid, but may help you...) you should make sure that you are closing ALL
jdbc objects (including resultsets and statements, i.e:
stmt.close();
rset.close();
If you aren't working with a connection pool, also make sure that you are
correctly creating and releasing (closing) connection objects.
Julio Serje
Calian Tech.
Kanata, ON, Canada.
----- Original Message -----
From: John Bateman <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, October 23, 2000 4:47 PM
Subject: RE: TOMAT slowing down a lot after a while
> Hey
>
> If you are running Linux, try going with Sybase ASE. Also if you have time
> to administer it, you could try IBM DB/2 developers edition.
>
> These are pretty much industrial database but they do have free developers
> version.
>
> Hope this helps.
>
> > -----Original Message-----
> > From: Federico Tello Gentile [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, October 23, 2000 4:23 PM
> > To: [EMAIL PROTECTED]
> > Subject: RE: TOMAT slowing down a lot after a while
> >
> >
> > 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.
> >
>
