> Incidentally, yesterday, working on the assumption that the problem is with > "false misses" in the cache, I implemented an alternative to > org.apache.shiro.session.mgt.eis.EnterpriseCacheSessionDAO, which also > extends CachingSessionDAO, but also writes sessions to the database and > reads from the database in the event of a cache miss. My sessions are quite > small, but this still might not be a good solution. However, if the problem > goes away, then I've definitely implicated the cache and not some other > thing that's causing my sessions to be invalidated.
I think this is a really good idea. This is how I typically structure my production applications: an enterprise cache for performance but the sessions are persisted to a backing store (e.g. NoSQL or RDBMS). Please keep us posted on your findings! Best, -- Les Hazlewood CTO, Katasoft | http://www.katasoft.com | 888.391.5282 twitter: @lhazlewood | http://twitter.com/lhazlewood katasoft blog: http://www.katasoft.com/blogs/lhazlewood personal blog: http://leshazlewood.com
