-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martin,
On 3/24/2009 12:06 PM, Martin Gainty wrote: >> On the other hand, a background thread (in the same JVM) that serially >> processes some jobs scheduled by request processors (say, like sending >> an email message) is often a good idea. Just as long as you don't run >> "new Thread().start()" during request handling, which is a bit scary. > > MG>whats the concern ..not identifying ThreadGroup?..checkAccess() error? > MG>thread already started? The concern is that remote clients can effectively create threads on your server. Make a lot of requests to a particular URL that creates a thread and soon you are doing any of the following: a) starving other threads b) running out of processes (process max) c) running out of memory Anything that needs to be asynchronous ought to at least use a thread pool / batch technique, rather than firing-off a new thread in response to a request. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAknJT/wACgkQ9CaO5/Lv0PCLOgCdHhbiSCVj6u6CkVOA58XbYQV5 ajwAnjhXzVj5UV6staG7zN3QfDGSCEVP =xzjx -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
