Latest revision as of 16:00, 7 December 2011

<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.

[edit] 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.