Hello! In the tomcat documentation:
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/coyote.html there is this: minProcessors The number of request processing threads that will be created when this Connector is first started. This attribute should be set to a value smaller than that set for maxProcessors. The default value is 5. is there a max limit that this value supports? In tomcat 4.0.6 I can set this as high as 2000 and it does spawn 2000 threads when it initially loads. With tomcat 4.1.27 this does not work. I have systems that have this setting set to a min of 400 and a max of 600, shortly after apache starts complaining that it cannot submit work to tomcat because tomcat is out of workers, checking the # of processes, tomcat is in the ~350 range, nowhere near 600. Tomcat 4.0.6 had quite a bit of logging info with regards to threads I can't find(sofar) any such info in tomcat 4.1.27. e.g. when a thread would start tomcat would put an entry in localhost_log or catalina_log. If threads were exausted it would say something like "no workers to process request, rejecting this connection". Been searching for any info I can find on maximizing the number of available threads on tomcat and sofar cannot come up with very much. Anyone know of a good resource for tuning thread levels? The system I am testing on is a Dual 3Ghz Xeon with 2MB L3 cache, 3GB ram, and Ultra 320 disks. I'm not a programmer, just one of the folks that runs the servers. My goal is to have 800 AJP13 threads and 800 HTTP threads(or whatever the tomcat 4.1.27 equivilent is I think there is a new term for them ......). I cannot figure out why the system doesn't spawn the threads. It doesn't spit out any errors it's like it decides to ignore that option completely. Even turning up debug shows nothing in the logs. I have gotten tomcat 4.0.6 to spawn as many as 3,000 threads(much beyond that and it fails to allocate more), without a hitch. had to recompile libpthread to do it though. I really like the idea of the jmx stuff in 4.1.27 and would like to keep using it, instead of 4.0.6 but finding info on increasing/managing the threads in 4.1.x seems sparse(to me anyways). OS is Redhat Enterprise ES 2.1. Using apache 2.0.45 with mod_jk as a front end to tomcat, also have a weblogic app server connecting to tomcat as well. is there any big benefits to upgrading to 4.1.29? someone forwarded an email to me mentioning a "known" problem with earlier versions of tomcat 4.1 "hanging". the tomcat version number isn't something I decided upon, the developers did. thanks nate --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
