Howdy, >In what moment new threads are created in Tomcat when it's running?
Under many possible circumstances: new webapp deployed, new request arrived and current # processors on the receiving connector less than max and all processors busy, some new JNDI resources (e.g. 3rd party datasource reaper thread), some app code (e.g. log4j's configureAndWatch call), many many. >Is there a thread pool? In case positive: For some things, notably request processors, there's a pool. >- What is the initial quantity of threads created? You specify it, see server.xml. >- What is the stagger algorithm? You didn't really mean to ask that in this context, did you? >- After created, when a thread terminates (end of life, release)? For request processors in current coyote, answer is when the server dies. But again there are many possible permutations. >- What means o large number of threads? Many users? Many sessions? Many >requests? Any and all of the above as well as none of the above. Consider for example a server configured with ten connectors, each with 100 min spare processors, one webapp per connector calling log4j's configureAndWatch -> 10*100 + 10 = 1010 threads. And that's just on startup, before receiving any requests or creating any sessions ;) 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]
