InfoCenter Home > 4.4.1.1.5: Using sessions in a clustered environmentConsider the following issues regarding how session management works within a clustered environment. Clustered environments include any environments in which requests are being handled by multiple Web servers, multiple application servers, or both. See section 7 for more about clustering and workload management. For use in a clustered environment, objects placed in persistent sessions must be serializableTo make your applications portable to a clustered environment, you must make any objects placed in a persistent session serializable. If you place an object that does not implement the Serializable interface, you lack a way to propagate the object with a given session, disallowing proper persistence among servlets in the cluster. For additional notes on programming for clustered environments, see the related information. Session binding occurs on a certain application server in the clusterWhen HttpSessionBindingListener and HttpSessionBindingEvent are used in a clustered Web server environment, the event is fired in the application server on which the session is currently being processed. The action will occur in situations where:
If the session times out, this (unbound) event may be fired in any one of the application servers in the cluster. Certain changes might require restarting all Session Managers in a clusterSee the related information for details. |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|