WAS v8.5 > WebSphere applications > Web applications > SessionsDistributed sessions
In a distributed environment, we can save sessions in a database using database session persistence.
When a session contains attributes that implement HttpSessionActivationListener, notification occurs anytime the session is either...
- activated (session is read to the memory cache)
- passivated (session leaves the memory cache)
Passivation can occur because of a server shutdown or when the session memory cache is full and an older session is removed from the memory cache to make room for a newer session. It is not guaranteed that a session is passivated in one application server prior to activation in another application.
Related concepts:
Sessions
Tasks: Managing HTTP sessions