This was a regression introduced with SHIRO-443 I have proposed a fix: https://github.com/apache/shiro/pull/34
Let us know how it goes. Also, you can set the sessionValidationInterval with for the default created scheduler via `sessionManager.sessionValidationInterval = 6000` but this will NOT be applied to a custom scheduler (which is your use case) But for your last post something like the following should work, and not create an NPE: [main] cacheManager = org.apache.shiro.cache.MemoryConstrainedCacheManager securityManager.cacheManager = $cacheManager # Set the timeout to one minute, so we don't have to wait so long sessionDAO = org.apache.shiro.session.mgt.eis.MemorySessionDAO sessionManager = org.apache.shiro.web.session.mgt.DefaultWebSessionManager sessionManager.globalSessionTimeout = 60000 sessionManager.sessionDAO = $sessionDAO securityManager.sessionManager = $sessionManager securityManager.sessionManager.sessionValidationInterval = 6000 On Thu, Jul 28, 2016 at 3:32 PM, smm <[email protected]> wrote: > I should also point out that this problem prevents setting a custom > securityManager.sessionManager.sessionValidationScheduler.interval . For > grins I tried this shiro.ini to see if I could work around the problem and > get to the testing I set out to accomplish: > > > > Unfortunately, this fails with an NPE: > > > > > > -- > View this message in context: > http://shiro-user.582556.n2.nabble.com/Shiro-443-prevents-custom-Session-Validation-Scheduler-tp7581185p7581186.html > Sent from the Shiro User mailing list archive at Nabble.com. >
