Load balancing appA on one set of hosts and accessed via http:/hostA/abc Load balancing appB on another set of hosts accessed via https:/hostB/abc.
We see jessionid.hostA and jsessionid.hostB in the apache log. The problem is stickiness seems to be broken only if someone goes to hostA first and then to hostB.
No, you cannot access both apps on the same host, e.g. http://hostA/abc and https://hostA/abc
Thanks for your response.
Millie
Andrew Miehs wrote:
Are you load balancing? or do you have two different applications on two different servers?
The cookie is attached to the host name. Therefore you will have two JSESSIONIDs
One cookie: hostA:JESSIONID and the other hostB:JESSIONID
Or do both hosts A and B have BOTH applications? IE:
Can someone access http://hostA/abc and https://hostA/abc ?
- If so - and these are two different appications - you will have problems.
Andrew
On May 16, 2005, at 4:54 PM, Millie Morton wrote:
As a systems admin I've set up the following
apache-2.0.54 tomcat-5.0.28
We are loadbalancing (tomcat) 2 different applications with the same path, one under SSL on hostA and the other unsecure on hostB.
Application A: http:/hostA/abc Application B: https:/hostB/abc
The problem is: if a user goes to Application A (on hostA) first and then to Application B (on hostB) we are seeing apache log entries with 2 JSESSIONIDS, one from hostA and one from hostB. This makes for stickiness problems as you can imagine.
Is there a way to fix this without changing the path for one of the apps?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Millie Morton Information Technology Services Yale University New Haven, CT 06520 203-432-9226
