Apache 1.3.x can have a maximum of something like 255 processes servicing requests. If
there are more active apache processes than Jetty threads you can get this problem. We use
mod_jk to connect from Apache 1.3 to Jetty, and have set the Jetty thread count to 256.
Note that it's still possible
to increase the 256 processes limit on 1.3
The MaxClients directive sets the limit on the number of simultaneous
requests that can be supported; not more than this number of child
server processes will be created. To configure more than 256 clients,
you must edit the HARD_SERVER_LIMIT
Each of our servers handles roughly 50k jsp pages + 450k other files
each day. We're using JBoss3.2.1 + Jetty 4.2.9.
Does anyone have a recommendation as to how many threads we should allow
Jetty to have? We've got it currently set to the default (100), but
periodicly we're running out of
Each of our servers handles roughly 50k jsp pages + 450k other files
each day. We're using JBoss3.2.1 + Jetty 4.2.9.
Does anyone have a recommendation as to how many threads we should allow
Jetty to have? We've got it currently set to the default (100), but
periodicly we're running out of threads
