This sounds to me as the pool has reached it maximal count on concurrent connections and the application doesn't give back a connection within the timeout of the request for a new connection.
- request the connections as late as possible. (E.G. don't hold a connection in a session or servlet, get it for each request) - release all connections as early a possible. (And don't forget one) This will decrease the number of concurrent connections for a given load. - If you still observe this behaviour, increase the max pool size and the timeout (don't know if this is possible with this driver) > -----Urspr�ngliche Nachricht----- > Von: Sean LeBlanc [mailto:[EMAIL PROTECTED]] > Gesendet: Dienstag, 4. Juni 2002 18:33 > An: 'Tomcat Users List'; 'Jacob Kjome' > Betreff: RE: MS Driver (again) > > > Thanks for the help. I saw this before, but after giving it a closer > look I realized I needed to add the appropriate jars and use the dbcp > factory class. Now that it actually at last connects, what is the best > way to use this? I stress-tested a bit, and I started to get > errors showing up in the log that say this in the stack trace: > > java.util.NoSuchElementException: Timeout waiting for idle object > at -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
