From tomcat-user-return-93692-apmail-jakarta-tomcat-user-archive=jakarta.apache.org@jakarta.apache.org Thu Feb 26 13:59:33 2004 Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org Received: (qmail 11955 invoked from network); 26 Feb 2004 13:59:33 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 26 Feb 2004 13:59:33 -0000 Received: (qmail 50223 invoked by uid 500); 26 Feb 2004 13:59:09 -0000 Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 50210 invoked by uid 500); 26 Feb 2004 13:59:09 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 50195 invoked from network); 26 Feb 2004 13:59:08 -0000 Received: from unknown (HELO intergate.bb-sw.de) (194.25.40.40) by daedalus.apache.org with SMTP; 26 Feb 2004 13:59:08 -0000 Received: from localhost (localhost [127.0.0.1]) by intergate.bb-sw.de (8.12.7/8.12.7/SuSE Linux 0.6) with ESMTP id i1QDx7eT023277 for ; Thu, 26 Feb 2004 14:59:07 +0100 Message-ID: <403DFBBB.1060503@bb-sw.de> Date: Thu, 26 Feb 2004 14:59:23 +0100 From: Christoph Fischer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: de, en-us, en MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Hanging tomcat processes on heavy access References: <20040226083312.17647.qmail@web40506.mail.yahoo.com> <403DD0B5.6040407@nerim.net> In-Reply-To: <403DD0B5.6040407@nerim.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AntiVirus: checked by AntiVir MailGate (version: 2.0.1.16; AVE: 6.24.0.5; VDF: 6.24.0.19; host: intergate) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hello and thank you for your response, until now it workes as I've set up the min.-processes up to 100 and changed the min and max heap to 256/512MB Chris jerome moliere wrote: > Oswald Campesato wrote: > >> Hello, Chris: >> >> I have a couple of suggestions (but no answers). >> 1) you can attach to a process with the 'truss' command and monitor >> the read/write activity of the process. Syntax, options, and >> examples of truss can be had via "man truss" or Google "Unix truss >> command." This *might* reveal something. >> >> 2) you can kill hanging processes and release the port via >> a Unix command (the name escapes me right now), which >> may help reduce the number of time you need to reboot >> >> 3) try experimenting with the min/max heap size for Java; >> perhaps you can set both of them to small values in a test >> environment to quickly reproduce the problem and use #1 >> >> Since other people can continue working normally, it does >> not appear that you've read the maximum number of socket >> connections (338, if I remember correctly). Did this problem >> start after having installed new software or changing the >> environment? Perhaps you can try "rolling back" to see if >> the problem disappears.... >> >> Cordially, >> >> Oswald >> >> >> >> Christoph Fischer wrote: >> >> Hello everyone, >> >> here is my configuration: >> linux server with tomcat 4.1.29 connected to apache 1.3.29 via nod_jk >> java version "1.4.2_03" >> >> from tomcat server.xml >> >> port="8009" minProcessors="5" maxProcessors="500" >> acceptCount="10" debug="0"/> >> >> At heavy access times the user gets a blank screen on the browser >> and on the server a java process is hanging. Tomcat is still working >> and responding to further tasks, but the 'hanging' processes will >> stay around until reboot. Unfortunately the hanging processes will >> also keep a socket connection on port 8009 to apache, so after some >> time the system hangs due to too much connections. >> >> I could rebuild this situation also with jmeter and a simple servlet >> which only responds a simple html site, so the problem couldn't come >> from my coding. >> >> How can I solve this problem ? Is it coming from tomcat, apache or >> mod_jk??? >> >> > Hi christopher, > I'd like to add that you may need to improve the mod_jk config using > arguments (parameters) like the TIME_WAIT ? could be helpful to > release more quickly connections.... > have you setted the KEEP-ALIVE parameter ? > > I guess that a deep look to you mod_jk configuration may solve much > troubles... > HTH > Jerome > > --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org