Return-Path: Delivered-To: apmail-apache-bugdb-archive@apache.org Received: (qmail 24689 invoked by uid 500); 27 Jun 2001 03:16:48 -0000 Mailing-List: contact apache-bugdb-help@apache.org; run by ezmlm Precedence: bulk Reply-To: apache-bugdb@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list apache-bugdb@apache.org Received: (qmail 24679 invoked from network); 27 Jun 2001 03:16:47 -0000 Received: from rodney.concentric.net (HELO rodney.cnchost.com) (207.155.252.4) by h31.sny.collab.net with SMTP; 27 Jun 2001 03:16:47 -0000 Received: from www2 (www5.rowe-clan.net [208.176.192.150]) by rodney.cnchost.com id XAA14860; Tue, 26 Jun 2001 23:16:53 -0400 (EDT) [ConcentricHost SMTP Relay 1.14] Errors-To: Message-ID: <023001c0feb7$4a3c25e0$96c0b0d0@roweclan.net> Reply-To: "William A. Rowe, Jr." From: "William A. Rowe, Jr." To: , , References: <20010627024610.3738.qmail@apache.org> Subject: Re: os-windows/7941: Apache hangs after around a day of use on medium load Date: Tue, 26 Jun 2001 22:11:08 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > >Description: > I have a production application running on Apache server with Tomcat as servlet engine. The apache server fails to respond after regular interval of once a day. > There is no response from Apache when it happens and killing apache process is the only way to get out of this mess. > All this time, if I try to run the app. through tomcat( port 8080),application is running fine. > > Need to know a solution sooner as this is becoming a big issue w.r.t dependability of Apache on Win2000 m/c. The number of hits is not that large. Just 20-30 users connected at all time - all day. There have been a number of patches, some quite subtle, that could have an effect on these problems. Please upgrade Apache to 1.3.20 (necessary to avert a denial-of-service attack) and Tomcat 3.2.2, the combination of which may impact your issue. If that doesn't solve the problem, please try to provide a useful amount of detail on the type of traffic that fails v.s. anything that still functions (does loading mod_status allow you to watch for dead connections, etc.) And you may wish to think about using the MaxRequestsPerChild argument. Although there would be up to a one minute hiccup, if you can time it about once a day that shouldn't be all too noticable, and is preferable to your current problem. The other obvious point, what modules are used/loaded on this server?