Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 50625 invoked from network); 3 Aug 2009 22:50:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Aug 2009 22:50:38 -0000 Received: (qmail 32756 invoked by uid 500); 3 Aug 2009 22:50:39 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 32674 invoked by uid 500); 3 Aug 2009 22:50:39 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 32663 invoked by uid 99); 3 Aug 2009 22:50:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Aug 2009 22:50:39 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [193.252.22.192] (HELO smtp6.freeserve.com) (193.252.22.192) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Aug 2009 22:50:30 +0000 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3627.me.freeserve.com (SMTP Server) with ESMTP id 597847000084 for ; Tue, 4 Aug 2009 00:50:09 +0200 (CEST) Received: from smtp.homeinbox.net (unknown [91.109.166.131]) by mwinf3627.me.freeserve.com (SMTP Server) with ESMTP id 2A5EC7000082 for ; Tue, 4 Aug 2009 00:50:09 +0200 (CEST) X-ME-UUID: 20090803225009173.2A5EC7000082@mwinf3627.me.freeserve.com Received: from localhost (localhost [127.0.0.1]) by smtp.homeinbox.net (Postfix) with ESMTP id 6737D1A4F7C for ; Mon, 3 Aug 2009 23:49:58 +0100 (BST) X-Virus-Scanned: Debian amavisd-new at homeinbox.net Received: from smtp.homeinbox.net ([127.0.0.1]) by localhost (server01.dev.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k5gwrR2JwemT for ; Mon, 3 Aug 2009 23:49:55 +0100 (BST) Received: from [192.168.0.9] (study03.dev.local [192.168.0.9]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.homeinbox.net (Postfix) with ESMTPSA id 4A1941A4F72 for ; Mon, 3 Aug 2009 23:49:55 +0100 (BST) Message-ID: <4A776993.2090704@apache.org> Date: Mon, 03 Aug 2009 23:49:55 +0100 From: Mark Thomas User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: Tomcat Users List Subject: Re: what exactly happens when timeouts are set and tomcat has outofmemory errors. References: <445305.44285.qm@web52607.mail.re2.yahoo.com> In-Reply-To: <445305.44285.qm@web52607.mail.re2.yahoo.com> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Madhuri Patwardhan wrote: > Hi, > > Can somebody go over the details of what exactly happens when tomcat instance has outOfmemory errors and there are following timeouts set in a loadbalancer worker config. > > This is my understanding. > > ping_mode=A, ping_timeout=10000, reply_timeout=60000 and recorver_options=3 > > If the timeouts are set as above then CPing/Cpong test for connect and prepost will work. When a new real request is sent to this tomcat instance, it should hit reply_timeout because it has outofmemory errors. That depends on the state of the JVM. It might appear to work normally, it might fail to respond at all. Once on OOM has occurred Tomcat has to be assumed to be in an unknown state and should be restarted. I have seen Tomcat instances apparently recover from an OOM. It all depends why the OOM occurred and what Tomcat was doing at the time. > Then depending on no. of retries set (it is default, for me so 2), this instance will be tried once again. Second time also it should not get reply within reply_timeout and at that point it should be marked in "ERR" state. > However, I don't see that. I don't see it being marked in "ERR" state. The state is still "OK" inspite of this tomcat instance having outofmemory errors. Could somebody explain what am I missing? In short, you are incorrectly assuming that once an OOM has occurred Tomcat will no longer respond to requests. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org