It can sometimes be useful to be able to preserve existing Sessions across restarts of Jetty. The org.eclipse.jetty.server.session.HashSessionManager 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.
A SessionManager does just what it's name suggests - it manages the lifecycle and state of Sessions on behalf of a webapp. Each webapp must have it's own unique SessionManager instance. Enabling persistence is as simple as configuring the HashSessionManager as the SessionManager for a webapp and telling it where on disk to store the sessions:
<Configure class="org.mortbay.jetty.webapp.WebAppContext"> . . . <Set name="sessionHandler"> <New class="org.mortbay.jetty.servlet.SessionHandler"> <Arg> <New class="org.mortbay.jetty.servlet.HashSessionManager"> <Set name="storeDirectory">your/chosen/directory/goes/here</Set> </New> </Arg> </New> </Set> . . . </Configure>
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:
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: