I have seen this scenario of many gets from the cache. In our case, our cache manager was Hazelcast, which means that with every get there is, at the very least, a deserialization that occurs. I concur with Jiggy that one get at the beginning of a web request should be sufficient. The approach that this "caching" is in the realm of a caching manager is certainly reasonable, but this seems to be a different sort of caching - call it local, request-specific caching.
Best, Dan -- View this message in context: http://shiro-user.582556.n2.nabble.com/Cache-called-too-many-times-per-request-tp6851915p6855818.html Sent from the Shiro User mailing list archive at Nabble.com.
