I have 2 virtual hosts running IBM HTTP server to serve up an IBM WAS application. I want to use Apache to load balance between these 2 virtual hosts and use sticky sessions (session replication isn't an option here). I have the following configuration for the load balancing: ============================================================ Proxy balancer://serverpool> # member 1 BalancerMember http://10.151.102.35:9080 # member 2 BalancerMember http://10.151.102.35:9082 </Proxy> ProxyPass / balancer://serverpool/ stickysession=JSESSIONID ProxyPassReverse / balancer://serverpool/ ============================================================ The balancing works fine between the two hosts, howver when I log in to the application, I am assigned a JSESSIONID as per-usual, but Apache still balances the rest of my session between the two servers. I am getting sesison id's like 000086NBUlF_C0_Wc73Qg4BJi5K:-1 I read that it was the colon : messing up the sticky session, but unfortunately, WAS will only let me specify : or + Has anybody else run into this problem? If so, what did you do to solve it? I'm tearing my hair out! Feel free to mail me at my corporate email below: Regards, James Clarke Junior Developer / Quality Engineer Pearson Phoenix E-mail: james.clarke@xxxxxxxxxxx This email may contain confidential material. If you were not an intended recipient, please notify the sender and delete all copies. We may monitor email to and from our network. This email was sent by a company within the corporate group owned by Pearson plc, registered office at 80 Strand, London WC2R 0RL, registered in England and Wales with company number 53723 and VAT number GB 278 5371 21. --------------------------------------------------------------------- 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
|