Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 60579 invoked from network); 12 Dec 2009 15:57:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Dec 2009 15:57:49 -0000 Received: (qmail 17458 invoked by uid 500); 12 Dec 2009 15:57:45 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 17366 invoked by uid 500); 12 Dec 2009 15:57:45 -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 17355 invoked by uid 99); 12 Dec 2009 15:57:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Dec 2009 15:57:45 +0000 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 (nike.apache.org: domain of rainer.jung@kippdata.de designates 195.227.30.149 as permitted sender) Received: from [195.227.30.149] (HELO mailserver.kippdata.de) (195.227.30.149) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Dec 2009 15:57:36 +0000 Received: from [192.168.2.115] ([192.168.2.115]) by mailserver.kippdata.de (8.13.5/8.13.5) with ESMTP id nBCFvFjH026736; Sat, 12 Dec 2009 16:57:15 +0100 (CET) Message-ID: <4B23BD5A.6090107@kippdata.de> Date: Sat, 12 Dec 2009 16:57:14 +0100 From: Rainer Jung User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 MIME-Version: 1.0 To: Tomcat Users List CC: Alessandro Bahgat Subject: Re: Tomcat 6.0.16 + mod_jk 1.2.19 - request threads hanging up References: <99C8B2929B39C24493377AC7A121E21F967C706AA2@USEA-EXCH8.na.uis.unisys.com> <26673416.post@talk.nabble.com> <4B1F877D.9090502@pidster.com> <4B2264F9.3030002@kippdata.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 12.12.2009 13:26, Alessandro Bahgat wrote: > On Fri, Dec 11, 2009 at 4:27 PM, Rainer Jung wrote: >> On 09.12.2009 12:18, Pid wrote: >>> >>> It could be, but while you're upgrading you might consider upgrading >>> HTTPD to the best available version too, 2.0.52 release date: 1 Oct >>> 2004. (That's 35 internet years ago.) >> >> ... and mod_jk 1.2.19 dates back to September 2006, so according to your >> math 21 internet years ago. There were so many bugs fixed since then, that >> you'll hardly find anyone that really tries to help debugging those old >> versions. At least use a recent mod_jk and look at >> >> http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html >> >> for some important hints about configuration. > > Thank you both for your advice. I'm pushing towards upgrading the > Apache+mod_jk stack as well. > Our last tests with the latest Tomcat and mod_jk still showed a lot of > CPU time being spent in sendbb methods, with some threads being stuck > in that method for long time. > > We actually found out a lot of "unrecoverable error 200, request > failed" error messages in the mod_jk log (roughly around 1k per hour), > so I'm starting to wonder if there's any issue with the firewalls and > the network infrastructure. What would you think about that? > > [Thu Dec 03 16:58:52 2009][31539:42688] [info] > service::jk_lb_worker.c (873): unrecoverable error 200, request > failed. Client failed in the middle of request, we can't recover to > another instance. > [Thu Dec 03 16:58:52 2009][31539:42688] [info] jk_handler::mod_jk.c > (2056): Aborting connection for worker=applprod The above two lines belong together, the next lines are something different. The pait [pid:tid} changed. The above lines are logged, whenever there was a problem sending back gthe response from Apache to the client/browser. It may happen, if a user in the meatime clicked on something else or pressed the reload button. If you get it a lot, maybe your app is to slow, your users are to nervous, or indeed there might be a network problem. Occasional occurrences are normal. > [Thu Dec 03 16:58:53 2009][31612:42688] [info] > jk_open_socket::jk_connect.c (450): connect to XXX.XXX.XXX.XXX:8009 > failed with errno=111 > [Thu Dec 03 16:58:53 2009][31612:42688] [info] > ajp_connect_to_endpoint::jk_ajp_common.c (872): Failed opening socket > to (XXX.XXX.XXX.XXX:8009) with (errno=111) > [Thu Dec 03 16:58:53 2009][31612:42688] [info] > ajp_send_request::jk_ajp_common.c (1247): (applprod05) error > connecting to the backend server (errno=111) > [Thu Dec 03 16:58:53 2009][31612:42688] [info] > ajp_service::jk_ajp_common.c (1867): (applprod05) sending request to > tomcat failed, recoverable operation attempt=1 errno 111 is "Connection refused", so either your Tomcat was down or something else blocked the connection. Regards, Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org