HTTP Sessions

1. Consider reducing the session timeout (default 30 minutes) and average session size to reduce memory and processing pressures.
2. Consider if session failover is required as it increases complexity and decreases performance. The alternative is to affinitize requests and surgically store any critical state into a database.
3. Use session persistence (database) or WebSphere eXtreme Scale over memory-to-memory replication.
4. Consider using timed updates to save session state.

For more information, see the HTTP section of the WAS traditional Profile chapter.

Previous Section (Tune a Thread Pool) | Next Section (Security Recipe) | Back to Table of Contents