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, non-persistent, 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.
This is delivered by a combination of the
DefaultSessionCache (to keep sessions in memory) and a
NullSessionDataStore (to avoid session persistence).
If you do nothing, Jetty will instantiate one of each of these objects for each context at startup time using hard-coded defaults.
To explicitly set up non-persisted sessions using modules, use both the
session-cache-hash and the
Enabling the modules allows you to configure behavior - see the L1 Session Cache for detailed information on configuration options for the
NullSessionDataStore has no customizable options.