Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

This feature will be available as of release 6.1.6rc0.

Persisting Sessions

It can sometimes be useful to be able to preserve existing Sessions across restarts of Jetty. The org.mortbay.jetty.servlet.HashSessionManager now supports this feature. If persistence is enabled, the HashSessionManager will save all existing, valid Sessions to disk before shutdown completes. On restart, the saved Sessions are restored.


The above example uses a configuration file suitable for the Context Deployer - you might want to check out the documentation for it.

Delaying Session Load

Sometimes you may need to ensure that the sessions are loaded AFTER the servlet environment has been started up (by default, sessions will be eagerly loaded as part of the container startup, but before the servlet environment has been initialized). For example, the Wicket web framework requires the servlet environment to be available when sessions are activated.

Using SessionManager.setLazyLoad(true), sessions will be loaded lazily either when the first request for a session is received, or the session scavenger runs for the first time, whichever happens first. Here's how the configuration looks in xml:

Code Block

<Set name="sessionHandler">
   <New class="org.mortbay.jetty.servlet.SessionHandler">
       <New class="org.mortbay.jetty.servlet.HashSessionManager">
         <Set name="lazyLoad">true</Set>

Enabling Persistence for the Maven Jetty Plugin

To enable session persistence for the maven jetty plugin, set up the HashSessionManager in the <configuration> section like so:


Contact the core Jetty developers at
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 from 1 day to full product delivery