A primitive way to confirm it is the odbc driver- use 2 web browsers to make 2 requests at the same time. Or use a benchmarking/stress testing tool to simulate many requests at the same time (like siege or similar).
To eliminate the problem - you may need to synchronize all database access so only one request may view/fax/whatever at a time. Or get a thread safe version of the odbc driver. After that - its out of my league. -Tim Geoff Peters wrote: > What alternatives would I have to that ODBC driver as a testing option? > > -----Original Message----- > From: Tim Funk [mailto:[EMAIL PROTECTED]] > Sent: June 11, 2002 9:32 AM > To: Tomcat Users List > Subject: Re: Tomcat Unexplained Shutdown > > > Quick stab in the dark - Since you are using an ODBC driver - I bet the > driver is not thread safe. So if tomcat is trying to serve 2 different > requests concurrently, it may be dying in native odbc code. > > -Tim -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
