Howdy, >We are not sure as to why this is happening. I read >somewhere that minProcessors/maxProcessors is only for >the request processing threads and not for the total >number of threads created by tomcat. If this is the
What you read is correct. >case then, how do we cap the total number of threads >being created by Tomcat ? I am concerned that we may >run out of memory if this continues. You can't strictly cap the total number of threads created by tomcat, as most of them are not under your control. That's the same as any app server. However, you can take some measurements to reduce the number of threads: - Don't have reloadable contexts if you don't need them - Remove the examples webapp and context >Any insights will be appreciated. If you're worried about the number of threads, you're in a good spot. There are a several things that would crash first under a heavy load, before the number of threads becomes an issue ;) Don't use the linux "top" command as an accurate measurement of the number of threads in the VM, as the JVM thread to OS thread mapping can be more than one to one. Use ulimit or whatever your system's equivalent is to raise the max number of threads allowed for the user that runs tomcat. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
