Return-Path: 
 <dev-return-57175-apmail-httpd-dev-archive=httpd.apache.org@httpd.apache.org>
Delivered-To: apmail-httpd-dev-archive@www.apache.org
Received: (qmail 95836 invoked from network); 8 May 2007 08:04:52 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 8 May 2007 08:04:52 -0000
Received: (qmail 4850 invoked by uid 500); 8 May 2007 08:04:55 -0000
Delivered-To: apmail-httpd-dev-archive@httpd.apache.org
Received: (qmail 4808 invoked by uid 500); 8 May 2007 08:04:55 -0000
Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
list-help: <mailto:dev-help@httpd.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@httpd.apache.org>
List-Post: <mailto:dev@httpd.apache.org>
List-Id: <dev.httpd.apache.org>
Delivered-To: mailing list dev@httpd.apache.org
Received: (qmail 4797 invoked by uid 99); 8 May 2007 08:04:55 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 May 2007 01:04:55 -0700
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: local policy)
Received: from [212.12.33.142] (HELO smile.2scale.net) (212.12.33.142)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 May 2007 01:04:47 -0700
Received: from dslb-084-060-240-188.pools.arcor-ip.net ([84.60.240.188]
 helo=[192.168.1.37])
	by smile.2scale.net with esmtpsa (TLSv1:AES256-SHA:256:NULL:N)
	(Exim 4.53)
	id 1HlKgK-0000u1-Ge
	for dev@httpd.apache.org; Tue, 08 May 2007 10:04:24 +0200
Message-ID: <46402F0F.3000200@2scale.de>
Date: Tue, 08 May 2007 10:04:31 +0200
From: Georg von Zezschwitz <gvz@2scale.de>
User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326)
MIME-Version: 1.0
To: dev@httpd.apache.org
Subject: Re: Bug 41897 / Session-Stickiness with mod_proxy_balancer
References: 
 <3B21A253728EA247A10A692547A271538DCAD0@EITO-MBX03.internal.vodafone.com>
 <4613B96B.602@apache.org> <C36E2BC2-60EB-4681-9635-FCC9A810900C@jaguNET.com>
 <4613C56C.7080305@2scale.de>
 <9D8FFB5C-F23B-4104-A687-4034ACA2E734@jaguNET.com> <46162B49.80703@2scale.de>
 <463F1BA4.2060707@apache.org>
In-Reply-To: <463F1BA4.2060707@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Ruediger Pluem wrote:
> -        for (i = 0; i < arr->nelts; i++) {
> -            const char *err = set_balancer_param(conf, cmd->pool, balancer, elts[i].key,
> -                                                 elts[i].val);
> +        else {
> +            if (params->nelts > 0 &&
> +                  (balancer->sticky || balancer->sticky_force ||
> +                   balancer->max_attempts_set || balancer->timeout)) {
> +                ap_log_error(APLOG_MARK, APLOG_WARNING, 0, cmd->server,
> +                         "repeated parameter definition for balancer %s "
> +                         "overwrites previous definitions",
> +                         balancer->name);
> +                balancer->sticky = NULL;
>
> Why resetting balancer->sticky here? It is not clear that the contents of
> balancer->sticky is changed. It makes sense to reset it if we have at least
> one "stickysession" parameter inside of params->elts so that we cleanly
> overwrite all the "stickysession" stuff then.
>   
What makes me a bit lost is the following configuration situation:

You declare a balancer:

<Proxy balancer://mycloud>
  BalancerMember ajp://192.168.1.1:5001 route=member1
  BalancerMember ajp://192.168.1.2:5001 route=member2
</Proxy>

Now I want to balance 2 paths:

<Location /app1>
  ProxyPass balancer://mycloud/app1 stickysession=JSESSION
</Location>

<Location /app2>
  ProxyPass balancer://mycloud/app2 stickysession=JSESSION
</Location>

The repeated ProxyPass definitions might give the impression that you 
can specify
different settings for /app1 and /app2 - e.g. stickysession parameters 
(which is not true).

Using an elegant:

<LocationMatch "/(app1|app2)">

is also not possible if the path element (/app1 vs /app2) has to be 
passed to the backend.

I am missing an elegant solution for mapping multiple paths to the same 
balancer.

Did I miss something here?

Best regards,


Georg