Hi Jeff, I'm glad you figured this out - yes, default ehcache settings for a cache region is a TTL of 2 minutes: Ehcache was evicting the Session entries without Shiro knowing about it.
For those that might come across this issue in the future, you can set ehcache config settings for Shiro's session cache as described here: http://shiro.apache.org/session-management.html#SessionManagement-EHCacheSessionCacheConfiguration Terracotta config is mentioned below if you want to use Terracotta to cluster those sessions. Maybe one day someone will contribute documentation about using other clustering options (e.g. Zookeeper). HTH, Les On Sun, Sep 25, 2011 at 1:06 PM, jeffp <[email protected]> wrote: > This is resolved. Looking back through the logs I noticed that ehcache was > not able to find any ehcache.xml definition and so the default provided by > ehcache was being used. > > The solution was to simply provide my own ehcache.xml and drop it into the > classpath. > > -- > View this message in context: > http://shiro-user.582556.n2.nabble.com/New-session-created-after-2-minutes-of-inactivity-tp6826476p6829888.html > Sent from the Shiro User mailing list archive at Nabble.com.
