Always-load-session
From Resin 3.0
(Difference between revisions)
| Line 1: | Line 1: | ||
| + | {{Cleanup}} | ||
[[Category:Configuration]] [[Category:Sessions]] | [[Category:Configuration]] [[Category:Sessions]] | ||
Revision as of 15:59, 7 December 2011
|
This article requires cleanup and may refer to a legacy version of Resin.
Please visit http://www.caucho.com/documentation/ for the most up-to-date documentation. |
<always-load-session/> tells Resin's persistent session manager to always load the session from the backend database, even if Resin thinks its cached session is up-to-date.
In general, <always-load-session/> should be false.
Example Scenario
If a load balancer is using an un-clustered set of backend Resin instances, the jdbc store with always-save-session and always-load-session should cause the session to be loaded from the database for each request.
The load-balancer is completely random in it's usage of the backend servers, the overhead of having Resin load and save the session from the database for every request is acceptable.
