Les Hazlewood-2 wrote
> A quick workaround is to just catch and ignore the
> exception and then issue the redirect.
Hi Les
Thanks for the response. I've tried wrapping the
SecurityUtils.getSubject().logout() method in a try/catch but the exception
isn't being caught by this catch block. Instead the error seems to be caught
by the faces servlet. I've tried catching both
java.lang.IllegalStateException and
org.apache.shiro.session.UnknownSessionException but neither actually get
caught.
The error message returned by the faces servlet is as follows
javax.servlet.ServletException: /app/index.xhtml at line 39 and column 82
action="#{logout.submit}": java.lang.IllegalStateException:
org.apache.shiro.session.UnknownSessionException: There is no session with
id [37de04fc-8ec2-48ea-8c14-aeb8053ebd7b]
Any ideas?
Kind Regards
Paul
--
View this message in context:
http://shiro-user.582556.n2.nabble.com/UnknownSessionException-when-calling-logout-method-using-Shiro-s-built-in-session-management-tp7578804p7578807.html
Sent from the Shiro User mailing list archive at Nabble.com.
