Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Add config option to use persistent session with Jetty

Description

I would like to be able to restart OpenNMS without logging everyone (well, me) out. That way for the rare times that a restart is required I can do so without anyone noticing.

Therefore we need to add support to configure the built-in Jetty instance to persist the sessions to disk and load on startup. Initial research indicates this is as simple as using the HashSessionManager and specifying a directory for the session data.

Acceptance / Success Criteria

None

Attachments

1

Lucidchart Diagrams

Activity

Show:

Benjamin Reed April 24, 2014 at 12:33 PM

In 1.12.7, Jetty has been changed to use a jetty.xml file which can be configured to handle issues like this.

Seth Leger November 25, 2013 at 11:53 PM

also mentions that this would be useful for seamlessly transitioning users to a new server in an HA setup, if implemented correctly.

Ron Roskens September 22, 2012 at 11:36 PM

The attached patch, 0001-Add-persistent-session-saving-to-JettyServer.patch adds a HashSessionManager to JettyServer.

While this initial part works, I've found that it doesn't persist any sessions because of java.io.NotSerializableExceptions' being thrown.

HybridOpenNMSUserAuthenticationProvider
SpringSecurityUserDaoImpl

Fixed

Details

Assignee

Reporter

Labels

Components

Fix versions

Affects versions

Priority

PagerDuty

Created September 13, 2012 at 4:12 PM
Updated January 27, 2017 at 4:21 PM
Resolved April 24, 2014 at 12:33 PM