On 7/28/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
> > Believe me, I wouldn't have gone to all that trouble if the session
> > data was available for me to get to the user attribute in the session.
>
> Interesting... I'd bet it was a peculiarity of the container's spec
> implementation. Did you say it was Jetty at that time too? I'm not at
> all familiar with Jetty, so it's just a guess.
>
> > This has stirred my curiosity. I'll give it another go for my current
> > project (we weren't using Jetty on the previous project) and report
> > back.
>
> Please do... I'd be intersted to know the answer as well :)
And the answer with Jetty 4.2.23 is:
java.lang.IllegalStateException
at
org.mortbay.jetty.servlet.AbstractSessionManager$Session.getAttribute(AbstractSessionManager.java:665)
at
com.verisign.mauth.server.admin.web.framework.SessionTimeoutListener.sessionDestroyed(SessionTimeoutListener.java:26)
at
org.mortbay.jetty.servlet.AbstractSessionManager$Session.invalidate(AbstractSessionManager.java:648)
at
com.verisign.mauth.server.admin.web.LogoffAction.doLogoff(LogoffAction.java:48)
at
com.verisign.mauth.server.admin.web.LogoffAction.unspecified(LogoffAction.java:57)
at
org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:256)
at
org.apache.struts.actions.DispatchAction.execute(DispatchAction.java:194)
at
com.verisign.mauth.server.admin.web.common.BaseDispatchAction.execute(BaseDispatchAction.java:121)
at
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419)
at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)
at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1192)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:412)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358)
at
org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:342)
at
com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)
at
com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)
at
org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:334)
at
com.verisign.mauth.server.admin.web.MessageFilter.doFilter(MessageFilter.java:30)
at
org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:334)
at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:286)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1807)
at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1757)
at org.mortbay.http.HttpServer.service(HttpServer.java:879)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:789)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:806)
at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:300)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:511)
Which is pretty much what I remember from the last time I tried this
and I believe I was working with a 4.x Tomcat container the last time.
My current project is the first one where I am using Jetty. The
location in my listener class where this exception is thrown is the
line where I try to get the "user" attribute from the session object
inside the sessionDestroyed() method.
You must live a blessed life or I a cursed one. ;-)
-Van
--
- Mike "Van" Riper
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
