Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 48258 invoked from network); 28 Jan 2009 16:44:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Jan 2009 16:44:03 -0000 Received: (qmail 24564 invoked by uid 500); 28 Jan 2009 16:43:49 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 24535 invoked by uid 500); 28 Jan 2009 16:43:49 -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 24524 invoked by uid 99); 28 Jan 2009 16:43:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Jan 2009 08:43:49 -0800 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [195.227.30.149] (HELO mailserver.kippdata.de) (195.227.30.149) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Jan 2009 16:43:42 +0000 Received: from [10.30.0.80] ([10.30.0.80]) by mailserver.kippdata.de (8.13.5/8.13.5) with ESMTP id n0SGhJT3020015 for ; Wed, 28 Jan 2009 17:43:19 +0100 (CET) Message-ID: <49808AF1.90502@kippdata.de> Date: Wed, 28 Jan 2009 17:42:25 +0100 From: Rainer Jung User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1b3pre) Gecko/20081204 Thunderbird/3.0b1 MIME-Version: 1.0 To: Tomcat Users List Subject: Re: does this mod_jk.log look healthy? References: <8cb75a4a0901270420i9f712aaqc163b0e4ada81034@mail.gmail.com> <497F19E9.6020200@kippdata.de> <8cb75a4a0901280300t434288c5j599611912d1375d5@mail.gmail.com> In-Reply-To: <8cb75a4a0901280300t434288c5j599611912d1375d5@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 28.01.2009 12:00, Arne Riecken wrote: > Thanks for Your answer. > > There are at least two (watchdog) ajp requests through the web server to the > workers every minute, and as i wrote, the ajp connection_pool_timeout ist > 600, connectionTimeout in Tomcats server.xml is accordingly 600000. So I > cannot image how the web server can be more idle than the pool timeout, even > at busy daytime, where the log messages also occure every few minutes? > > We will look forward to upgrade to 1.2.26. The pool is local to any Apache httpd process. I assume your requests get distributed to more than one httpd process. You can log the process ID of the httpd process with %P in the access log, and if you are using a multi-threaded MPM (worker) also the thread id (%{tid}P). 1.2.27 would be better than 1,2,26 ;) Regards, Rainer > 2009/1/27 Rainer Jung > >> Without additional error level messages that's OK. The web server noticed, >> that there was no connection to the backend open and will transparently >> create a new one. This could happen, if your web server is more idle than >> configured with the JK connection pool timeout or Tomcat's >> connectionTimeout. >> >> You should update to 1.2.27, it's better than 1.2.23 :) --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org