Thank you guys. Sam, I totally agree with you. Increasing max threads will only delay my worries. My ISP has increased max thread size to 40 so at least I'm unable to reproduce my problem on one or two users.
I've tried to get the JConsole to work with SSH but with no luck, seems to be tricky... I'll try more another day. Running JConsole on my local development server works great and I can see clearly that 3 threads is enough for one user. One thread is mysteriously always busy, one thread is in use shortly on every request and if I try hard refreshing I can get another thread running. I'll talk to my nice ISP and see if they can help me running the JConsole. Malin On 12/7/06, Sam Gendler <[EMAIL PROTECTED]> wrote:
On 12/7/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > Increase the max thread size on your tomcat context threadpool. It > looks to me like the log message is telling you a max of 10 is > currently allocated for this purpose now. (an abnormally low number) > If this is really only occuring with one or two users on the system, 10 threads should be enough, since no browser will open more than 2 connections to the server at any single instant. It would appear that something is preventing threads from returning to the pool as soon as the request is completed. Bumping the max threads up to a higher number will give you temporary relief, but doesn't fix the underlying problem that is preventing you from reusing threads efficiently. 10 is a very low number, however, and you may well find that bumping the number to 100 will instantly give you enough headroom that you never see the problem again (with reasonable load, anyway). But since this is a hosted server, it is entirely possible you can't bump the maxThreads number. In that case, you can complain to your ISP or else you will have to figure out why the threads aren't being reused. --sam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
