Are you using the JDBC-ODBC bridge packaged with jdk? If so, it may be the cause of the problem. Try using another driver (type 3 or 4?). I've learned that the JDBC-ODBC bridge is not suggested for production use. HTH.
:~) Ricky Y. Artigas Analyst/Programmer / Database Administrator Information Technology Division Easycall Communications Phils., Inc. > ------------------------------- > IMPORTANT NOTICE: > This message (and any attachment hereto) may contain privileged and/or > confidential information specific to EasyCall. If you are not the intended > addressee indicated in this message, you may not copy or disseminate this > message (or any attachment hereto) to anyone. Instead, please destroy this > message (and any attachment hereto), and kindly notify the sender by reply > email. Any information in this message (and any attachment thereto) that > do not relate to the official business of EasyCall shall be understood as > neither given nor endorsed by the company. > > > -----Original Message----- > From: Vara Prashanth [SMTP:[EMAIL PROTECTED]] > Sent: Thursday, September 27, 2001 7:22 AM > To: [EMAIL PROTECTED] > Subject: Tomcat 3.2.2 crashes with JDBC > > Hello all: > > I am facing a problem when I use JDBC to query a microsoft access database > on a win2K advanced server! I was testing the system for stability using > JMeter which essentially passes requests to a servlet. The servlet in turn > queries an access database and responds. When the number of threads > increases I get an error while closing the DB connection and Tomcat > crashes > producing a log file. I will be happy to send out the log file if > required. > Can you please help me solve the problem? Is this a problem with the > access > driver or with access or with my servlet or tomcat(although very > unlikely!) > > Thanks in advance > > Prashanth > > > > _________________________________________________________ > > Do You Yahoo!? > > Get your free @yahoo.com address at http://mail.yahoo.com > >