-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Vishwajit,
On 5/19/2009 6:08 PM, Pantvaidya, Vishwajit wrote: >> No, Tomcat uses precisely 1 thread to handle each incoming HTTP >> request. If keepalives are used, multiple requests may be handled >> by the same thread before it is returned to the pool, or different >> threads may be used to serve different requests from the single >> connection, but in either case, no more than 1 thread will be used >> to service a single HTTP request. > > [Pantvaidya, Vishwajit] Could this happen if upon my http browser > request, the app could be spawning multiple redirects in quick > succession leading tomcat to create multiple threads. Any other > thoughts why I could be seeing tomcat spawn threads in multiples of > 4? No, the only thing your browser can do in order to activate a thread is to make a request. If a single page contains many items to download (images, CSS files, scripts, etc.) then the browser may make several requests to the server simultaneously. Most web browsers limit their simultaneous requests to a single server to 4, so maybe that's what you're observing. The weird thing is that you're observing 4 threads doing something /without/ any requests being made. > [Pantvaidya, Vishwajit] Ok thanks. "httpd -l" showed perfork.c. I > guess that means we are using prefork MPM. So our cachesize should be > 1? Our mod_jk version is 1.2.15 - will that also auto-detect the > cache-size? Yes and yes. > [Pantvaidya, Vishwajit] I agree - but again as I mentioned above > because the admin will be conservative about any changes, I need to > have a strong reason. How's this for a compelling reason: your server keeps locking-up in its current configuration. > Also when you say let the connection stay > alive, does that mean let the TP-Processor thread remain in Waiting > state / Runnable state? I mean that you shouldn't set any connection_pool_timeout on any of your workers. There really isn't a need to set this unless you are having some kind of problem IMO. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkoVe7oACgkQ9CaO5/Lv0PAbdQCeK088qxz+9/TNBnJgfHBg6Gyz 7+4AoI6fbXdn4Sh6kR9QaQhvK/jmHWpF =frxU -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
