You cannot expect timeout to occur at exactly 20 minutes after the previous request because the JVM may be busy doing something else. Having said that 5 minutes delay is too much. Check whether the server is busy processing some other request which may result in the timeout thread not getting CPU cycles.
We found the same thing in Websphere. The timeout value prevents the user from using the session, but the actual session does not get cleared for some time after. This is just the way it is, unfortunately
Originally posted by David O'Meara: We found the same thing in Websphere. The timeout value prevents the user from using the session, but the actual session does not get cleared for some time after. This is just the way it is, unfortunately
If it prevents the user from using it after 20 minutes (and not 25 minutes)then it should be ok even if the other listener methods are invoked later.
ashok sashrith
Greenhorn
Joined: Jan 31, 2005
Posts: 12
posted
0
David, There is confusion over here. Could you little more elaborate on "The timeout value prevents the user from using the session, but the actual session does not get cleared for some time after".
0
