Anonymous | Login | Signup for a new account | 12-17-2024 08:55 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0002268 | [Resin] | minor | always | 12-19-07 11:18 | 12-20-07 14:47 | ||||
Reporter | sam | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | high | Resolution | fixed | ||||||
Status | closed | Product Version | 3.0.24 | ||||||
Summary | 0002268: mod_caucho not using consistent secondary server | ||||||||
Description |
(rep by D Wigenfors) We are using resin-pro-3.0.24, and we are using mod_caucho with apache 2.2 for load-balancing between the resin-servers. I've done a test with a 4 server setup, one apache/mod_caucho, and 3 resins. If I access the site with no cookie, I get a sessioncookie from a random resin-server, for example: cbaCKfGlR-2aM6tPNfoBr. Subsequent requests stay on that server, and the way we verified this is by using a webpage printing out the session-cookie and the current app-server. If server 'c' is then stopped, subsequent requests should, as I understand it, go to server 'b', but when reloading the page printing out instance-names, It gets thrown between the two remaining servers. First server 'a', and after a reload, server 'b', then server 'a' again etc. When server c is started again, the request returns to server c and stays there for subsequent requests. |
||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
There are no notes attached to this issue. |
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
27 total queries executed. 25 unique queries executed. |