This is entirely dependent upon what code creates a session in your application.
For example, although it might just be you interacting with the webapp, 3rd party code or frameworks might be creating a session without your knowledge. I've seen this if something sits 'higher up' in the filter chain than the ShiroFilter and that filter uses a session before Shiro has a chance to handle the call. I've also seen this on JSP pages that don't use <%@ page session="false" %> at the top of the page - some servlet container implementations will trigger session creation during page rendering (I've seen this from time to time on Tomcat, but don't know why). So I would do some debugging and put a break point when a session is being saved - that way you can see what in the stack trace is triggering session creation without your knowledge. HTH, Les On Thu, Mar 14, 2013 at 3:07 PM, NabbleSometimesSucks <[email protected]> wrote: > Would that then explain why there are three entries in Redis when I just go > to my website. Haven't even logged in yet. But I notice three different keys > in Redis created. They have three different ids (All look like SessionIDs, > but there is only one that is the actual SessionID stored in the cookie. > > Here are two of them > > redis 10.0.30.76:6379> keys * > 1) "a7b6ff70-29be-4827-b049-00d45360c5f0" > 2) "9885180b-8d92-440f-892c-2562d0c92849" > 3) "7b357f05-9139-46e1-a25c-68280e3b7e44" > redis 10.0.30.76:6379> hgetall "a7b6ff70-29be-4827-b049-00d45360c5f0" > 1) "startTimeStamp" > 2) "1363298546774" > 3) "host" > 4) "127.0.0.1" > 5) "sessionID" > 6) "a7b6ff70-29be-4827-b049-00d45360c5f0" > 7) "timeOut" > 8) "1800000" > 9) "lastAccessTime" > 10) "1363298546774" > redis 10.0.30.76:6379> hgetall "7b357f05-9139-46e1-a25c-68280e3b7e44" > 1) "startTimeStamp" > 2) "1363298544814" > 3) "host" > 4) "127.0.0.1" > 5) "sessionID" > 6) "7b357f05-9139-46e1-a25c-68280e3b7e44" > 7) "timeOut" > 8) "1800000" > 9) "lastAccessTime" > 10) "1363298544814" > redis 10.0.30.76:6379> > > As you can see they all look the same except for the SessionID. But I am the > only one connecting to Redis right now. > > Thanks > > Mark > > > > > > -- > View this message in context: > http://shiro-user.582556.n2.nabble.com/There-might-be-something-wrong-with-the-Cache-interface-tp7578385p7578403.html > Sent from the Shiro User mailing list archive at Nabble.com.
