Not sure if I understood, however:
1) No, because you are using "nofailover=On"
2) It will be lost. You have to implement clustering (session
replication) among Tomcats to keep the session active if one TC server
goes down (AND remove the nofailover from Apache).
-----Original Message-----
From: nskarthik [mailto:nskarthik.k@xxxxxxxxx]
Sent: Monday, June 24, 2013 7:36 AM
To: users@xxxxxxxxxxxxxxxx
Subject: Proxy Balancing Not working as Expected
Hi
SPEC : Apache 2.22
O/s :Suse ent-10
LBS for 2 Tomcat's with Session based
Config currently
#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
<IfModule !mod_proxy.c>
LoadModule proxy_module modules/mod_proxy.so </IfModule>
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so LoadModule
proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_connect_module modules/mod_proxy_connect.s
ProxyPass /balancer-manager !
ProxyPreserveHost On
<Proxy balancer://mycluster>
BalancerMember http://192.168.4.32:8085/ loadfactor=50 #node1
BalancerMember http://192.168.4.32:8086/ loadfactor=50 #node2
ProxySet lbmethod=bytraffic timeout=15 </Proxy>
ProxyPass / balancer://mycluster/ stickysession=JSESSIONID|jsessionid
nofailover=On
ProxyPassReverse / balancer://mycluster/
#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Problem
a)If any one IP/PORT of node is down , Does the above config route to
another node which is alive one ?
b)What would happen to the session already latched to the node. ?
I have tried evaluating both cases , but failed
with regards
karthik
--
View this message in context:
http://apache-http-server.18135.x6.nabble.com/Proxy-Balancing-Not-workin
g-as-Expected-tp5006574.html
Sent from the Apache HTTP Server - Users mailing list archive at
Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
This e-mail (and attachment(s)) is confidential, proprietary, may be subject to copyright and legal privilege and no related rights are waived. If you are not the intended recipient or its agent, any review, dissemination, distribution or copying of this e-mail or any of its content is strictly prohibited and may be unlawful. All messages may be monitored as permitted by applicable law and regulations and our policies to protect our business. E-mails are not secure and you are deemed to have accepted any risk if you communicate with us by e-mail. If received in error, please notify us immediately and delete the e-mail (and any attachments) from any computer or any storage medium without printing a copy.
Ce courriel (ainsi que ses pièces jointes) est confidentiel, exclusif, et peut faire l’objet de droit d’auteur et de privilège juridique; aucun droit connexe n’est exclu. Si vous n’êtes pas le destinataire visé ou son représentant, toute étude, diffusion, transmission ou copie de ce courriel en tout ou en partie, est strictement interdite et peut être illégale. Tous les messages peuvent être surveillés, selon les lois et règlements applicables et les politiques de protection de notre entreprise. Les courriels ne sont pas sécurisés et vous êtes réputés avoir accepté tous les risques qui y sont liés si vous choisissez de communiquer avec nous par ce moyen. Si vous avez reçu ce message par erreur, veuillez nous en aviser immédiatement et supprimer ce courriel (ainsi que toutes ses pièces jointes) de tout ordinateur ou support de données sans en imprimer une copie.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|