Hi, I'm using an embedded Jetty for our web application. A long time ago we have tied our usage checks to http sessions. This makes use of the fact that all sessions are properly invalidated when the server shuts down.
I have revisited this topic again now and I'm seeing that the http sessions are no longer invalidated when the server shuts down. Digging into DefaultSessionCache's shutdown method I see that to get proper session invalidation I should not use a SessionDataStore (https://github.com/eclipse/jetty.project/blob/jetty-9.4.x/jetty-server/src/main/java/org/eclipse/jetty/server/session/DefaultSessionCache.java#L143). At the same time it seems I cannot go without a SessionDataStore as AbstractSessionCache's doStart method insists on using one (https://github.com/eclipse/jetty.project/blob/jetty-9.4.x/jetty-server/src/main/java/org/eclipse/jetty/server/session/AbstractSessionCache.java#L203). Is this inconsistency expected? How would I code my way around it? -dirk _______________________________________________ jetty-users mailing list jetty-users@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users
