Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jetty-users] NoSqlSessionManager will always invalidateSessions upon context stop

I tried to configure the 2 instances of jetty-8 with MongoSessionManager (cluster), the session objects persisted to MongoDB just fine, 
BUT when I stopped 1 instance of jetty, my session attribute is gone.

I took a look in the method `NoSqlSessionManager#invalidateSessions` which will be called upon stopping jetty.

#1 : Is this expected behavior (when stopping jetty, it'll clear session's objects ) ?
#2 : how can I prevent this behavior ?


Back to the top