|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 3116 | minor | always | 12-04-08 09:43 | 03-26-09 16:46 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 3.2.1 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.0 | ||
|
|
|||||
| 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: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||