Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 2886 invoked from network); 5 Feb 2010 17:16:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Feb 2010 17:16:35 -0000 Received: (qmail 51722 invoked by uid 500); 5 Feb 2010 17:16:31 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 51658 invoked by uid 500); 5 Feb 2010 17:16:31 -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 51647 invoked by uid 99); 5 Feb 2010 17:16:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Feb 2010 17:16:31 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of aw@ice-sa.com designates 212.85.38.228 as permitted sender) Received: from [212.85.38.228] (HELO tor.combios.es) (212.85.38.228) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Feb 2010 17:16:23 +0000 Received: from localhost (localhost [127.0.0.1]) by tor.combios.es (Postfix) with ESMTP id 672292260D3 for ; Fri, 5 Feb 2010 18:16:01 +0100 (CET) Received: from tor.combios.es ([127.0.0.1]) by localhost (tor.combios.es [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gBPkhoZ6OfDW for ; Fri, 5 Feb 2010 18:16:01 +0100 (CET) Received: from [192.168.245.129] (montserrat.wissensbank.com [212.85.37.175]) by tor.combios.es (Postfix) with ESMTPA id 1A92D226097 for ; Fri, 5 Feb 2010 18:16:01 +0100 (CET) Message-ID: <4B6C5238.80300@ice-sa.com> Date: Fri, 05 Feb 2010 18:15:36 +0100 From: =?ISO-8859-1?Q?Andr=E9_Warnier?= Reply-To: Tomcat Users List User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Missing files for mod_jk References: < ECBE70BA1D83964490525E064C9F96F96390696CBE@SBS.tecracer.local><99C8B2929B39 C24493377AC7A121E21F96C4148A82@USEA-EXCH8.na.uis.unisys.com>,<99C8B2929B39C24493377AC7A121E21F96C4148B79@USEA-EXCH8.na.uis.unisys.com> <99C8B2929B39C24493377AC7A121E21F96C4148D09@USEA-EXCH8.na.uis.unisys.com> In-Reply-To: <99C8B2929B39C24493377AC7A121E21F96C4148D09@USEA-EXCH8.na.uis.unisys.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Caldarale, Charles R wrote: >> From: Alexander Diedler [mailto:adiedler@tecracer.de] >> Subject: AW: Missing files for mod_jk >> >> Sorry, it is 1024 KB, sure, just to fast tipped into the keyboard. > > So again, why did you change it from the default? > >> worker.list= worker3,loadbalancer,jkstatus > > I see no declarations for worker3. > >> ok, I adjust maxThreads to 1000 > > I'm certainly not an expert in configuring mod_jk, but don't you need to keep the AJP maxThreads setting in sync with the worker.worker?.connection_pool_size setting? Picking arbitrary values will get you into trouble. > From the mod_jk docs (workers.properties) : connection_pool_size : Usually this is the same as the number of threads per web server process. JK will discover this number for the Apache web server automatically and set the pool size to this value. Under Windows, Apache has a single child, multi-threaded. In Alexander's configuration, the maximum number of threads for Apache is set at 1920 (?). That in itself already looks to me like a big number, but I don't know the real load of the server. The question here is whether ALL requests going through Apache get passed through to Tomcat via mod_jk, and whether there are requests to Tomcat that go directly to Tomcat without going through Apache. If all requests go through Apache, and all of them then go from Apache to Tomat, then I would say that the number of threads in Apache should be set to roughly the number of expected maximum concurrent requests, and that the maxThreads of the AJP Connector in Tomcat should be set to the same number. That is, the total number of threads in the two Tomcats, because the Apache/mod_jk is balancing between them. And also because each Apache thread will make maximum one connection to one Tomcat thread. (Each Apache thread + connection + Tomcat thread may process more than one request however, if there are KeepAlive connections involved). Then I would let this run for a while, and examine the Apache logs, and the mod_jk log at the Apache level. Either one of them will record whether there are cases were the threads setting is too low, and requests are being turned away. Also, assuming that these parameters : Initial memory pool: 256 MB Maximum memory pool : 1024 MB are actually equivalent to -Xms and -Xmx settings of the JVM, I would set them equal both to the same value, to gain some efficiency. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org