-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Simão,
On 11/12/2009 5:19 AM, Simão Fontes wrote: > Thanks for the help Christopher, I'm going to try and use your option to > bind things to the 127.0.0.1 in order to have a safe number of threads. Yeah, I think that's a good idea (it was mine, after all:) because you basically have two choices: (Assuming app A calls app B via HTTP:) 1. Configure app A with X threads in the pool and configure app B to have X + Y threads in the pool (to potentially allow X threads from A to use X threads in B, /plus/ users who are trying to directly use B) 2. Configure A and B to share X threads for outside requests, and configure a loopback-only pool containing X threads just in case 100% of incoming requests on A or B end up being A->B requests You can slightly lower the number of threads required to serve all requests. Also, if you use fewer than X threads in your loopback-only pool, you can guarantee that you won't deadlock because the requests aren't competing for the same set of threads (that is, it's not possible for an outside-request thread to wait forever for a loopback-thread because loopback-threads never loopback themselves). > When I try this option I'm going to feedback to the mail list so the > answer is registered. Great. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkr8JyAACgkQ9CaO5/Lv0PBOZQCeJE2q7GlKAFWWWKnWMDtc+O4g lHUAnjkLQhrJ2leHqwfub9UQrjAzf5dX =bT0b -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
