Mladen, Thank you very much for your reply. I didn't catch cachesize relates to concurrent users, in this case I will have to change a lot of workers.
So I assume that there are (currently) no recommendations regarding a maximum total worker.cachesize for a single IIS5 server, correct? Also, a little comment: it would be useful to have a default higher than 10 for cachesize, or maybe a global setting in the isapi_redirect.properties file. Thanks again, br1. ----- Original Message ----- From: "Mladen Turk" <[EMAIL PROTECTED]> To: "Tomcat Users List" <users@tomcat.apache.org> Sent: Wednesday, January 11, 2006 5:29 PM Subject: Re: Small connection problems with JK 1.2.15 and IIS 5 > br1 wrote: > > Hello, > > > > I am new to the list but I must say I used it a lot to find things in the > > past years. > > This time I am facing a problem or two but not finding a solution.. small > > problems luckily. > > > > (2) > > [Fri Jan 06 15:17:20 2006] [warn] jk_ajp_common.c (2138): Unable to get > > the free endpoint for worker MYWORKER from 20 slots > > [Fri Jan 06 15:17:20 2006] [info] jk_ajp_common.c (2152): can't find free > > endpoint > > > > Increase the cachesize for the worker. > The value should reflect the number of concurrent users on the system. > The above messages means that you have more then 20 concurrent users > connected. > > > According to a few posts I found I added connectionTimeout="0" to some > > tomcats and raised the cachesize of some workers that were > > giving problems (worker.MYWORKER.cachesize=20) > > > > > Now I still get the error (1) a couple of times a second and the error (2) > > a few times the day. > > > > My questions at this point would be: > > 1- Are the above entries caused by the new JK 1.2.15 or I did have the same > > problems and I didn't notice? (the log level was set to > > "emerg") > > See above comments. > > > 2- I applied connectionTimeout="0" to Tomcats 5.5.x. Is this also needed > > for older Tomcat versions 5.0/4.1.7/4.0.6 - though in the > > docs the parameter was not documented for the AJP connector? > > You don't need this for 5.x (by default connectionTimeout is disabled), > but you need that for 4.x (connectionTimeout defaults to 1 minute). > > > 4- In the AJP documentation the min and maxProcessors are deprecated. What > > should one use instead? They saved my life with Tomcat 4. > > maxThreads. > > > > > 6- Too many questions? :-) > > > > No :) > > Regards, > Mladen. > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
