-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bharath,
On 3/3/2010 12:21 PM, Bharath Vasudevan wrote: > Let me explain the scenario. When tomcat gets a request, it does a socket > send to some other process to handle the request and then respond. This > would happen fast. But assuming 20k client requests come in at the same > time, the server would try to allocate 20k threads and handle it. Mostly the > system would trash and go down. > > But if it was to be handled gracefully, we can have the threads pick up the > request throw it in a queue and let the worker threads work and respond. Let > me know if I am missing something here. Wouldn't you have to limit that queue, otherwise you might never catch up with the requests and run out of memory? Limiting the work queue size versus the thread pool size are equivalent in terms of user experience: at some point, the remote requests are refused. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuOpKMACgkQ9CaO5/Lv0PB/GQCgk+dKujEGRKF69ZVjmn7uWcVA rbAAniTg+2nvvOygxACU1tNCmRauitsS =wO/z -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
