Re: [users@httpd] stickysession at mod_proxy_balancer

[dom <apache@xxxxxxxxxx>]

Hi Oliver,

1. no, i don't.. thats the strange thing.. just see in the accesslog:
[debug] mod_proxy_balancer.c(41): proxy: BALANCER: canonicalising URL
//produrl/site
[debug] mod_proxy_balancer.c(803): proxy: Entering byrequests for BALANCER
(balancer://prod)
[debug] mod_proxy_balancer.c(396): proxy: BALANCER (balancer://prod) worker
(http://192.168.1.1:8001) rewritten to http://192.168.1.1:8001/site
[debug] mod_proxy.c(736): Running scheme balancer handler (attempt 0)

2. don't really understand your question. my 'backendservers' produce a cookie
with teh attribute 'sessionkey' and use this for the own 
sessiondeclaration, so
i thought to use that one. i (the webserver) just added ".A_" at the 
end of the
sessionkey for identify the 'route' to apache, but i guess thats not the only
thing i need to do? i can produce every cookie-attribute you like, thats not
the problem.. whats jvmroute? i'm not using tomcat, we use a self written
webserver..

i thought it should be easy: a have allready a sessionkey, so thats nice. then
the backendwebserver now which server he is, so he set another attribute, and
add this to the sessionkey (sessionkey.route) and this route is 
definied on the
BalanceMember.. but i guess i missunderstand the topc.. :-(

bye
dom

Quoting Oliver.Schaudt@xxxxxxxxx:

> Hi dom,
>
> 1. Do you see some lines like "proxy: BALANCER: Found value 
> 12721798.A_ for stickysession sessionkey" in the "error_log" ?
> 2.Do you have set your session-identifier nameinside your servers 
> behind Apache to "sessionkey" and the route alias jvmroute to your 
> "A_" and "B_" ? If not than it won't work.
>
> Bye
>
> Oliver
>
> ________________________________
>
> Von: dom [mailto:apache@xxxxxxxxxx]
> Gesendet: Di 17.01.2006 16:23
> An: users@xxxxxxxxxxxxxxxx
> Betreff: [users@httpd] stickysession at mod_proxy_balancer
>
>
>
> hi,
>
> i'm using apache 2.2 because of the balancing module, but i can't 
> figure out why
> the 'stickyness' doesn't work.
>
>
> -snip-
> LogLevel debug
> ProxyPass / balancer://prod/ stickysession=sessionkey nofailover=On
>  <Proxy balancer://prod>
>   BalancerMember http://192.168.1.1:8001 <http://192.168.1.1:8001/>  route=A_
>   BalancerMember http://192.168.1.2:8001 <http://192.168.1.2:8001/>  route=B_
>  </VirtualHost>
> -snip-
>
> the sessionkey-coockie is set to something like 12721798.A_
>
> after a few clicks (depends from 2 to 15) i get connectet to the 
> second Member,
> but don't see why! any ideas?
>
> when i have a look at the logfile, i never see some information about the
> coockie or so.. :-(
>
> thanks in advance
> dom



---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx