Timeout will not send anyone anywhere. When the session expires it cleans up all the objects in the session's attributes. If the objects are of type HttpSessionBindingListener then an event is thrown against them.
The best way to handle timed out users is to attach an object of HttpSessionBindingListener to their session, When that object recieves the unbound event do whatever is needed to be done to clean up.
Note - (I got burned on this) at the unbound event the session object no longer references any attributes (or maybe it is just some) so the object of the above type should have enough intelligence in it to handle the actions you want to perform at the end.
for example you had a session attribute storing the logged in user name, dont expect that attribute to be available after the unbound event.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 22, 2001 3:51 PM
To: [EMAIL PROTECTED]
Subject: session timeout handling
When a Tomcat session times out does it send you to a preset error page?
What is the mechanism there?
What is the best way to handle timed out users?
