On 4/20/05, LeeAnn Pultz <[EMAIL PROTECTED]> wrote: > This is not a memory leak in the application - we have hooked up a profiler > to the application and watched the actual memory usage when causing this > issue to happen. We have lots of memory available, are nowhere near the > Xmx limit, and the machine has lots of memory available over and above the > Xmx limit. > > 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]
