Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 98753 invoked from network); 16 May 2006 16:57:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 16 May 2006 16:57:09 -0000 Received: (qmail 26428 invoked by uid 500); 16 May 2006 16:57:03 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 26374 invoked by uid 500); 16 May 2006 16:57:03 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 26363 invoked by uid 99); 16 May 2006 16:57:03 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 May 2006 09:57:03 -0700 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [192.146.101.72] (HELO sw3.lexmark.com) (192.146.101.72) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 May 2006 09:57:00 -0700 Subject: JKStatus Bug? To: dev@tomcat.apache.org X-Mailer: Lotus Notes Release 5.0.12 February 13, 2003 Message-ID: From: dhay@lexmark.com Date: Tue, 16 May 2006 12:56:35 -0400 X-MIMETrack: Serialize by Router on smtp5b/Lex/Lexmark (Release 6.5.5|November 30, 2005) at 05/16/2006 12:56:38 MIME-Version: 1.0 Content-type: text/plain; charset="us-ascii" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi, We're using 3 load-balancers to seperate our requests up (client and admin etc.) and numerous tomcat servers (we're running Apache in front). We need to be able to disable servers on a load-balancer level - so I need to disable 2 of the 3 load balancers on a particular server, say. We can do this fine using the jkstatus page, but when the machines are restarted, the changes don't seem to have been persisted. And it seems that workers.properties is not fine-grained enough to handle this? Our setup is below... Any ideas how to get around this? cheers, David mod-jk.conf snippet: JKMount /framework/admin/* adminloadbalancer JKMount /framework/httpadaptor/* adaptorloadbalancer JkMount /framework/* clientloadbalancer # if you wanted to only load-balance a sub-context, you could # map the module differently, such as: # JkMount /myContext/* loadbalancer JkMount /status/* jkstatus workers.properties: worker.LAUREL.type=ajp13 worker.LAUREL.lbfactor=1 worker.LAUREL.cachesize=25 worker.LAUREL.port=8009 worker.LAUREL.host=LAUREL.mw.prtdev.lexmark.com worker.BLUFF.type=ajp13 worker.BLUFF.lbfactor=1 worker.BLUFF.cachesize=25 worker.BLUFF.port=8009 worker.BLUFF.host=BLUFF.mw.prtdev.lexmark.com worker.adminloadbalancer.type=lb worker.adminloadbalancer.method=B worker.adminloadbalancer.sticky_session=1 worker.adminloadbalancer.sticky_session_force=1 worker.adminloadbalancer.local_worker_only=1 worker.adminloadbalancer.balanced_workers=BLUFF,LAUREL worker.clientloadbalancer.type=lb worker.clientloadbalancer.method=B worker.clientloadbalancer.sticky_session=1 worker.clientloadbalancer.sticky_session_force=1 worker.clientloadbalancer.local_worker_only=1 worker.clientloadbalancer.balanced_workers=BLUFF,LAUREL worker.adaptorloadbalancer.local_worker_only=1 worker.adaptorloadbalancer.type=lb worker.adaptorloadbalancer.method=B worker.adaptorloadbalancer.sticky_session=1 worker.adaptorloadbalancer.sticky_session_force=1 worker.adaptorloadbalancer.balanced_workers=BLUFF,LAUREL worker.jkstatus.type=status worker.list=jkstatus,adminloadbalancer,clientloadbalancer,adaptorloadbalancer --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org