On 07/10/2010 23:17, Christopher Schultz wrote: > Rob, > > On 10/7/2010 12:59 PM, Rob G wrote: >> Recently migrated a production site (mixture of Servlets and JSPs) >> from Oracle Application Server to Apache/Tomcat. Since then we have >> seen numerous HTTP Error 503 - Service unavailable errors at peak >> times when site is under load. mod_jk.log has the following error >> message(s): > >> [2184:1952] [error] jk_lb_worker.c (1473): All tomcat instances >> failed, no more workers left > > Just to reinforce a comment by Andre, I think you might want to compare > the request processor counts you have for Tomcat versus mod_jk: the > default maxThreads for a Tomcat <Connector> is 200, while your > MaxClients settings might be different on your Apache httpd configuration. > > If you have httpd.MaxClients=250 and connector.maxThreads=200 then you > have a deficit of 50 who will get 503 errors if they try to access your > webapp during peak load. > >> Apache: 2.2.16 > > I believe that only the Worker MPM is available on Microsoft Windows. > Have you explicitly configured an MPM? > >> worker.worker1.cachesize=10
Is this info in the original email? (If so, I think my mailer isn't behaving well). p --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
0x62590808.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
