On Fri, Sep 24, 2010 at 5:29 PM, Brian <bbprefix-m...@yahoo.com> wrote: > Hi Christoper, >
> The sessions expire if 2 hours have passed, and if that happens, the system > forwards them to another page. > I mean, in my programming I already considered what should happen if the > session suddenly expired, and it should not arrive to this point. > > Thanks! > You can't be sure that's whats happening though. The browser can make its own rules with session cookies. Unlikely but possible for the cookies to be deleted sometimes. Some people may not accept session cookies in the first place. Are you encoding the urls for sessions too? Where's the bean being set in an Interceptor, in a filter, on an earlier page in the session? Is it possible that you've missed a route to the pages which should always have this bean? Is it possible that people are directly navigating to the page that throws the error (say via a bookmark, or got a cached search engine result)? My advise would be (assuming you have an access log enabled that contains the session id). Look at the access log. Try to figure out the route the person took through your site. How long between page views? Was there some detail that they entered in the bean which was unserialiasble etc. I doubt anyone here can tell you the answer to your new problem, it too dependant on your new environment, however hopefully we will point you in a good direction to start looking. Also you can start a new thread as Christopher put but mark it OT. (if you don't believe tomcat is at fault). Regards, Wesley Acheson --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
