Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 07F79EF97 for ; Mon, 3 Dec 2012 10:42:15 +0000 (UTC) Received: (qmail 85954 invoked by uid 500); 3 Dec 2012 10:42:11 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 85890 invoked by uid 500); 3 Dec 2012 10:42:11 -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 85865 invoked by uid 99); 3 Dec 2012 10:42:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Dec 2012 10:42:10 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.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; Mon, 03 Dec 2012 10:42:02 +0000 Received: from [192.168.245.129] (p549E9069.dip0.t-ipconnect.de [84.158.144.105]) (Authenticated sender: andre.warnier@ice-sa.com) by tor.combios.es (Postfix) with ESMTPA id 7058E3C0B08 for ; Mon, 3 Dec 2012 11:42:28 +0100 (CET) Message-ID: <50BC81E4.2020704@ice-sa.com> Date: Mon, 03 Dec 2012 11:41:40 +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: Mod_jk - loadbalancer References: <50BC78B6.4090007@ice-sa.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Orhan, 1) do not "top-post". It is difficult to follow the logical flow of the conversation when you do that. Orhan Karasakal wrote: > > On Mon, Dec 3, 2012 at 12:02 PM, Andr� Warnier wrote: > >> Orhan Karasakal wrote: >> >>> Hi, >>> >>> I use mod_jk loadbalancing. (JkMount /WebApp/* loadbalancer ) >>> I want to use only one loadbalancer. Can I set specific url after >>> balancing >>> ? >>> >>> For example, firstly every request will go to loadbalancer. >>> Then if request is /WebApp/A*.com, it will go to node1. If request >>> /WebApp/B*.com, it will go to node2 >>> >>> worker.loadbalancer.balance_**workers=node1,node2. >>> >>> I may not understand correctly what you really want, but from your >> explanation above, it does not look like "load balancing". What you seem >> to want is to forward some requests to one Tomcat back-end (worker1), and >> some others to another Tomcat back-end (worker2). >> >> If that is the case, you should do this : >> >> JkMount /Webapp/URL-1/* worker1 >> JkMount /Webapp/URL-2/* worker2 >> >> > But firstly I want to send requests to loadbalancer and then according to > url, sending the other nodes. > I have a lot of nodes and I have to use loadbalancer for every request Then I believe that the answer to your question is : no, you cannot do that. Mod_jk does not foresee such a case, as far as I know. But mod_jk, like Tomcat, is open-source. So you could take the code and modify it as per your wishes. Or you could post an enhancement request. Or you could change your architecture, and introduce an intermediate level of load-balancing : 1st level : Apache httpd with mod_proxy_http and load-balancing, balances to 2d level : Apache httpd with mod_jk, balances to 3d level : Tomcat workers --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org