Status/Resolution/Reason: Closed/Withdrawn/Duplicate
Reporter/Name(from Bugbase): Daniel Short / Daniel Short (Daniel Short)
Created: 07/01/2015
Components: Core Runtime, Session Management
Versions: 11.0
Failure Type: Enhancement Request
Found In Build/Fixed In Build: CF11_Final /
Priority/Frequency: Normal / Some users will encounter
Locale/System: English / Win 2012 Server x64
Vote Count: 3
Duplicate ID: CF-3941961
Problem Description:
With a non-clustered group of CF instances, Session data is stored on each individual server. This requires that we have sticky sessions configured at a load balancer level, or try to configure CF clustering, which is untenable with really large CF installations.
I want to be able to have my servers in a round-robin rotation, and go to a central session store for all session data. That store should be whatever I want it to be, with a common interface. Either a database, or disk somewhere, or a nosql caching cluster.
Steps to Reproduce:
Set up two CF instances in a round-robin load balancer. On Server 1, set a session variable.
Reload a page to dump the session.
Actual Result:
Depending on the server, you'll get either session values from Server 1 or Server 2
Expected Result:
Pull a session value from a central session store based on CFTOKEN or JSESSIONID, regardless of the server the user lands on.
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 4015158
External Customer Info:
External Company:
External Customer Name: Daniel
External Customer Email:
Attachments:
Comments: