On tomcat 3, I even tried manipulating the thread pool settings (since in 4 and 5 those are handled inside tomcat).
But I'm seeing the same problems on 3, 4 and 5.0
> In fact, I can cause the error to happen every single time, simply by > hitting the first web page (login page) of the application - I don't have > to log in, or do any "work". All I have to do to get the error to happen > is hit 18-19 different instances of the web application, watch the Active > thread count go up to 100 and tip over the tomcat.
This isn't related to the minProcessors, maxProcessors & acceptCount settings for your connector in your server.xml by any chance?
Regards, -- Jason Bainbridge http://kde.org - [EMAIL PROTECTED] Personal Site - http://jasonbainbridge.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
LeeAnn Pultz
ExtraView Corporation
[EMAIL PROTECTED]
831-461-7100 x115
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
