I think there is a bug slipped in the latest 0.4.3 release.I get a
org.apache.shiro.subject.ExecutionException:
java.lang.IllegalStateException:
org.apache.shiro.session.InvalidSessionException:
java.lang.IllegalStateException

when a user logouts from a page that has @RequiresRoles
annotation.This started happening at revision r2171.Full stack trace
below
2012-03-22 01:06:30.035:WARN::/users.layout:logout
org.apache.shiro.subject.ExecutionException:
java.lang.IllegalStateException:
org.apache.shiro.session.InvalidSessionException:
java.lang.IllegalStateException
        at 
org.apache.shiro.subject.support.DelegatingSubject.execute(DelegatingSubject.java:382)
        at 
org.tynamo.security.services.impl.SecurityConfiguration.service(SecurityConfiguration.java:104)
        at $HttpServletRequestFilter_81124445d4c.service(Unknown Source)
        at $HttpServletRequestHandler_81124445d51.service(Unknown Source)
        at 
org.apache.tapestry5.services.TapestryModule$1.service(TapestryModule.java:852)
        at $HttpServletRequestHandler_81124445d51.service(Unknown Source)
        at $HttpServletRequestHandler_81124445d4b.service(Unknown Source)
        at org.apache.tapestry5.TapestryFilter.doFilter(TapestryFilter.java:171)
        at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
        at 
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
        at 
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
        at 
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
        at 
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
        at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
        at 
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
        at org.mortbay.jetty.Server.handle(Server.java:326)
        at 
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
        at 
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
        at 
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
        at 
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

Regards
Dimitris Zenios

On Mon, Mar 19, 2012 at 5:06 AM, trsvax <trs...@gmail.com> wrote:
> That's interesting. I did not know you could bind an abstract class instead
> of an interface.
>
> --
> View this message in context: 
> http://tapestry.1045711.n5.nabble.com/tapestry-security-0-4-3-released-tp5574027p5576063.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to