Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@www.apache.org Received: (qmail 61989 invoked from network); 13 Nov 2003 16:44:23 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 13 Nov 2003 16:44:23 -0000 Received: (qmail 63990 invoked by uid 500); 13 Nov 2003 16:44:07 -0000 Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 63969 invoked by uid 500); 13 Nov 2003 16:44:07 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 63929 invoked from network); 13 Nov 2003 16:44:06 -0000 Received: from unknown (HELO mail22.messagelabs.com) (62.231.131.211) by daedalus.apache.org with SMTP; 13 Nov 2003 16:44:06 -0000 X-VirusChecked: Checked X-Env-Sender: david.oxley@workplace-systems.plc.uk X-Msg-Ref: server-19.tower-22.messagelabs.com!1068741845!337663 X-StarScan-Version: 5.1.13; banners=workplace-systems.plc.uk,-,- Received: (qmail 3884 invoked from network); 13 Nov 2003 16:44:05 -0000 Received: from smtp-2.star.net.uk (212.125.75.71) by server-19.tower-22.messagelabs.com with SMTP; 13 Nov 2003 16:44:05 -0000 Received: (qmail 11021 invoked from network); 13 Nov 2003 16:44:05 -0000 Received: from twexchangesvr.teleware.co.uk (HELO intranet-svr.teleware.co.uk) (195.216.12.194) by smtp-2.star.net.uk with SMTP; 13 Nov 2003 16:44:05 -0000 Message-ID: <3FB3B403.3050902@workplace-systems.plc.uk> Date: Thu, 13 Nov 2003 16:40:35 +0000 From: Dave Oxley MIME-Version: 1.0 To: Tomcat Developers List Subject: Tomcat 5.0.14 and JK loadbalancing Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 I have 4 load balanced JK (1.2.5) workers. When I select to stop Tomcat (5.0.14), which takes a while to shut down (because of some daemon threads in our app) a 400 bad request is returned to the browser even though there are other JK workers that could be used. A couple of causes spring to mind, but I don't know which one is true. Does it take a while for mod_jk to learn about the stopped status of the JK worker? Is it a bug with JK or Tomcat 5? JK load balancing was not designed for fault tolerance? I would appreciate some advice/explanation as this is about to become our standard setup. Cheers. Dave. ________________________________________________________________________ This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org