Hello, and thank you for that,
Yes, I am timing the session out and trying to handle the result. I have:
HttpSession objSession = request.getSession(true);
String sessionStatus = (String) objSession.getAttribute("sessionStatus");
if (sessionStatus == null) {
forward off to JSP
}
Now sessionStatus is getting caught – fine, but when I try and redirect to a JSP after
that, nothing happens. I originally tried mapping.findForward (Struts),
response.sendRedirect and forwarding using RequestDispatcher. I have tried
getSession(true) and false. What implications (if any) does session timeout have in
terms of forwarding after the session is invalidated?
Many thanks
G.
Jerald,
> session.setMaxInactiveTimeout(-1);
Yeah, this is a bad idea. The session will never go away by itself. This
*requires* the user to press a logout button, and for you to explicitly
call session.invalidate(). Users frequently do not log themselves out,
and their sessions will never die. You will eventually run out of memory.
If you need a long timeout, just make it really long (like a couple of
hours). There's usually no good reason to make it -1.
> PS is the session time out linked wirth inactivity? My session
> attribute only persists as long as I am using the app.
That's exactly how the 'inactive' timeout works.
-chris
> ATTACHMENT part 2 application/pgp-signature name=signature.asc
---------------------------------
Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download
Messenger Now
