Anonymous | Login | Signup for a new account | 10-08-2024 14:58 PDT |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0003116 | [Resin] | minor | always | 12-04-08 09:43 | 03-26-09 16:46 | ||||
Reporter | ferg | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | Platform | |||||
Status | closed | OS | |||||||
Projection | none | OS Version | |||||||
ETA | none | Fixed in Version | 4.0.0 | Product Version | 3.2.1 | ||||
Product Build | |||||||||
Summary | 0003116: session timeouts | ||||||||
Description |
(rep by Richard Grantham) Yes, the logout code calls session.invalidate() and it works fine. I have some application logic in SessionListener.sessionDestroyed(...) which does some housekeeping after someone presses logout or their session times out, so it's important it's called. I'm finding that the session does not time out in the configured time (60 seconds) when, for instance, you close the browser, so SessionListener.sessionDestroyed() is not called. |
||||||||
Steps To Reproduce | |||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed. 25 unique queries executed. |