Thanks for replying to me. But I am not much aware about apache. I started it just before sometime ago. So please can you confirm it how can I do following:- Apache --- mod_jk connector ---tomcat Caching by mod_disk_cache and mod_cache Now if I changed any static file at tomcat(that is already cached at apache) must be re-cached in further request without shutting down apache and tomcat. Is it possible ? if so please can you give me guide me for configuration the same? Thanks a lot.. -----Original Message----- From: David Cassidy [mailto:david@xxxxxxxxxxxxx] Sent: Tuesday, February 26, 2008 7:20 PM To: users@xxxxxxxxxxxxxxxx Subject: Re: Server hanging with requests in "W" state Whats your timeout and keepalivetimeout settings set to ? If you have them more than 15 secs ? then you'll DOS yourself IE will hold open connections to the server for as long as it can... On Tue, 2008-02-26 at 09:29 +0100, pthyseba@xxxxxxxxxxxxxx wrote: > Hello, > > > On 25/02/2008, pthyseba@xxxxxxxxxxxxxx <pthyseba@xxxxxxxxxxxxxx> wrote: > >> We're having some strange problems with our webservers (https), which > >> are > >> Apache 2.0.52 on RHEL4 and 2.0.46 on RHEL 3. > > > > This could be due to MSIE's duff SSL implementation. Do you have > > something like this in your SSL config? > > > > BrowserMatch ".*MSIE.*" \ > > nokeepalive ssl-unclean-shutdown \ > > downgrade-1.0 force-response-1.0 > > > > > > > We do have this kind of line in our SSL configuration. However, we have > also seen this problem (512 W's with increasingly high "SS" values in > server-status, until even server-status can no longer be requested) on our > non-ssl web servers, albeit a lot less frequently (possibly because of > lower load triggering our scenario less frequently). > > I'm wondering what the technical (apache, sockets, OS,...) reason is for > the absence of some "Apache kill switch" which would terminate (that is, > free the apache slot and make it available to another client) a connection > with an "SS" value greater than some threshold - or is this supposed to be > solved by any of the apache Timeout settings? > > If not, I'll have to dig further into the plugins we're running. > > Is there a good overview available which explains the relationship between > Apache timeout settings and e.g. worker.properties (mod_jk) timeout > parameters (e.g. parameter1 >= parameter2) ? The documentation of each > package seems to only explain its own configuration directives, but I'm > thinking our problems may be related to some not-so-good combination of > timeout settings (at the moment they all have values > 0 and < infinite > though). > > Thx, > > Pieter > > > > noodl > > > > --------------------------------------------------------------------- > > The official User-To-User support forum of the Apache HTTP Server Project. > > See <URL:http://httpd.apache.org/userslist.html> for more info. > > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|