Hi Milos, Yes, those 3 lines are all that is usually needed.
However, I can't see how that exception can be thrown - higher in the call stack, the Shiro Filter will 'touch' the session to ensure its last access timestamp is updated. If it was successful in the Filter, I can't see how the session would be expired only nanoseconds later in your controller. Is this easily reproducible? Can you submit a test case? Regards, Les On Thu, Apr 28, 2011 at 2:17 AM, milosm <[email protected]> wrote: > I came to conclusion that all I need is: > > ... > Subject currentUser = SecurityUtils.getSubject(); > currentUser.logout(); > return "redirect:/login.do"; > > But the thing is that I get: > "org.springframework.web.util.NestedServletException: Request processing > failed; nested exception is java.lang.IllegalStateException: > org.apache.shiro.session.UnknownSessionException: There is no session with > id [429202b5-6405-4d9e-ac0f-7c824c33eaad]" > > Here is the trace: > http://shiro-user.582556.n2.nabble.com/file/n6312554/logout.do.htm > logout.do.htm > > -- > View this message in context: > http://shiro-user.582556.n2.nabble.com/Forget-RememberMe-tp6305821p6312554.html > Sent from the Shiro User mailing list archive at Nabble.com.
