Non-Clustered Session Management: Memory

Non-Clustered Session Management: Memory
Previous	Chapter 10. Session Management Home	Next

Contact the core Jetty developers at www.webtide.com

private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services for sponsored feature development

Non-Clustered Session Management: Memory

Non-clustered, in-memory-only is the default style of Session Management. In previous versions of Jetty this was referred to as "hash" sessions, as they were stored in a HashMap in memory. When using the Jetty distribution, if you do not configure any session module, this will be enabled by default.

Specifically, Jetty will hook up:

A DefaultSessionIdManager

Produces unique session ids and supports cross-context dispatch re-use of session ids

A HouseKeeper

Scavenges for expired sessions every 10 mins

A DefaultSessionCache per context

Keeps session objects in memory

A NullSessionDataStore per context

No persistence of sessions

If you wish to change any of the default configuration, enable the session-cache-hash module.

Previous	Top	Next
Session Configuration and Use Cases	Home	Non-Clustered Session Management: File System